Update server broken?

---

I‘ve released a new version of pimatic-echo yesterday, but the update doesn’t show up I’m pimatic. Also on the plugins page of pimatic.org it still shows the old version of the github page.

Is there something wrong with the update server? @mwittig could you take care of this?

I’ve checked the plugin update site from pimatic:

http://api.pimatic.org/plugins?version=0.9.54 delivers the old version of pimatic-echo and http://api.pimatic.org/plugins shows the latest version. Seems that there is some issue with the update site.

Sorry for the delay. The update server should be back to normal now.

@mwittig Problems are back. See https://forum.pimatic.org/topic/4800/pimatic-echo-0-5-6
Is there anything I can do when releasing my plugins?

I think the problem an issue related to hitting a quota for the Npmjs-API used by the update server.Update Server will be restarted. Let’s see how this goes

My stats plugin is checking daily around 1:00 if plugins are outdated. For that i’m using the function getOutdatedPlugins(). As far as I could trace this function calls registry.npmjs.org. Is that the api you are referring to?
If this is the case and the quota is rate limit based, I could spread the update calls in time.

@bertreb I don’t hope that the update server queries the npm registry every time that http://api.pimatic.org/plugins is called. If there really is a quota problem, then why don’t we just let every pimatic installation use the npm registry directly? It’s even already implemented. We just have to remove the call to http://api.pimatic.org and go directly to https://registry.npmjs.org

@michbeck100 i’m not using the api call but directly the function pluginManager.getOutdatedPlugins(). And that traces to the function getPluginInfoFromNpm(). That function is calling “https://registry.npmjs.org” directly.
In an earlier version I did the check at 00:00. That could have caused the problem.

I changed the ‘Outdated Check’ to once a day with a few hours random variation. Starting the daily check at the time pimatic started or the device was reloaded, so not at 00:00 anymore.
I didn’t got any error messages since the update.

I would like to start the discussion again. I’ve checked the changelog of pimatic-echo and it seems that the problems are there since I’ve removed the peedDependencies from the package.json (version 0.5.6). This was because newer node versions don’t support this anymore. Could this be the reason that the update server doesn’t list newer versions > 0.5.4 of the plugin?

I verified the behavior. I added peerDependencies to the latest pimatic-echo version and now the newest plugin version is found again.