It’s important to use the right terms here. I don’t see any add-ons in that list that comes from the Marketplace and it’s failing on the JavaScript Transformation which is an official add-on, not one from the Marketplace.
There was at least one other report of add-on installations failing so it might be the case that jfrog is down again. I just tried to bring up that repo and it’s requiring a login.
@kai (not sure who else to tag), did something change on jfrog to all of suddenly require a login to access the jfrog repo? Is this related to moving this stuff to GitHub?
No, I am not aware of any changes and the bindings are all available without any authentication needs:
➜ curl --output test.jar https://openhab.jfrog.io/artifactory/libs-milestone/org/openhab/addons/bundles/org.openhab.binding.adorne/3.4.0.M3/org.openhab.binding.adorne-3.4.0.M3.jar
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 32908 100 32908 0 0 38733 0 --:--:-- --:--:-- --:--:-- 39176
I would assume that in @icompas’ case there was either an Internet connection hiccup or one of the bindings has some missing dependency, which we didn’t notice yet. @icompas Maybe you can reduce the list of the installed bindings temporarily to see, if the add-on installation then succeeds. If so, you should be able to figure out which binding is causing the issue.
Currently, I downloaded the addons repo and installed it. That works fine for me.
At a later time I will try moving back to the remote option and will see if that works again.
I did not have any internet issues in the last days. So, it is a bit weird.
There did seem to be a change that started to ask me and others (@jwiseman) for login details when using these links below, which is the URL that a new PR in the addons repo recommends that you use to give to people to test the PR build:
Strangely when I hit refresh without logging in (as I have no account to login with) it would sometimes still download the file, but it seems to now be worse and always require the login. Where and to who should this be reported to?
The Ookla’s Speedtest Binding in the marketplace uses this same URL structure from the jfrog server.
I don’t know just shared my experience as I observed that behavior for a few days.
Testing it again I just saw that it is possible to access and browser through the repo/directories again.