wpackagist.org no longer fetching latest updates from WP

[allen-mckenzie]

Having to manually refresh the plugins I need to run updates for in order to install and update them with Composer.

[dear-leader]

I'm experiencing the same issue. Any updates?

[handpressed]

I noticed my fork had also stopped updating — something to do with the WP API returning 404s for discontinued plugins and themes. I updated to the GitHub pull request from June — #314 — which fixed it. My fork is public: https://wpackagist.handpressed.net

[NoelLH]

Thanks for spotting that link @handpressed and deploying the branch. I think the framework change PR with that fix is about ready to merge, but we've been busy and trying to sort out a hopefully-future-proof infrastructure change to get it deployed while moving to the latest PHP. That's coming along with use on another project, and hopefully we'll get Wpackagist moved over in the next couple of weeks.

[strarsis]

I can confirm for some plugins (TI Wishlist Plugin). When the plugin is manually refreshed, the new version is shown immediately in the search results. But composer cannot find it when updating to that new version, even after waiting 10 Minutes.

[allen-mckenzie]

It takes about an hour for the refreshed plugin to show up via composer. So far performing an update has been a matter of check the admin for updates, go through my composer list and see which plugins are in my composer.json for wpackagist, search for each plugin, refresh, wait an hour, update via composer and go on with my day. Makes for a long update process but it does eventually show up.

[NoelLH]

Thanks @allen-mcnichols, I suspected that may be the case. I think there is a job which runs every couple of minutes which is supposed to pick up queued updates, which I suspect isn't working as intended, and one that runs hourly which is.

When we get to rolling out the update and new infrastructure I'll try to work out what's going on and if all else fails try to find a way to increase the frequency of the full updates.

[timnolte]

This issue is seriously hampering development work that is dependent on the latest release of a plugin. I've refreshed the plugin on wpackist.org and it's showing the new version number but no number of composer clear-cache & composer update ... is working. This is a real big pain.

[NoelLH]

Hi @timnolte, I have had time only to get as far as deploying untested staging implementation of the new, significantly refactored codebase. Please feel free to try the untested https://staging-wpackagist.out.re/ in place of the normal repo domain and let me know how you get on. I'll be having a closer look at whether it's actually working as expected when time allows.

[timnolte]

Hi @timnolte, I have had time only to get as far as deploying untested staging implementation of the new, significantly refactored codebase. Please feel free to try the untested https://staging-wpackagist.out.re/ in place of the normal repo domain and let me know how you get on. I'll be having a closer look at whether it's actually working as expected when time allows.

Thanks @NoelLH

[hphoeksma]

Hi @timnolte, I have had time only to get as far as deploying untested staging implementation of the new, significantly refactored codebase. Please feel free to try the untested https://staging-wpackagist.out.re/ in place of the normal repo domain and let me know how you get on. I'll be having a closer look at whether it's actually working as expected when time allows.

Hi @NoelLH - when trying this url instead of the normal domain, composer throws me a not found error:
The "https://staging-wpackagist.out.re/packages.json" file could not be downloaded (HTTP/1.1 404 Not Found)

[NoelLH]

@hphoeksma thanks, that was a pretty big oversight! I carefully put the SQLite database in a shared location to support horizontal scaling, but forgot the output files that are the whole point of the process..

Fixed now, hopefully.

[hphoeksma]

@NoelLH - yes, working fine now :-) Thanks!

[abdusfauzi]

@NoelLH i visited the staging site, and tried to manually update after I search storefront, and this error pops up. Just letting you know. I wanted to help, but my knowledge about this error is beyond me.

Thanks for the hard work 👍

[strarsis]

Will the staging site replace the current wpackagist site when everything is finished?