New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TransportException 404 Not Found for packagist.org urls #940
Comments
|
As of last week this is happening multiple times a day. After having seemingly been almost unseen for months. Looks like a recent regressions perhaps? I'm also seeing it on Travis CI now, which is a first. https://travis-ci.org/wikimedia/mediawiki/jobs/422335462 Note that the run-time there is also measured. Travis clocks it at 154s (2 minutes and 34 seconds), which is far less than the previously stated age of "older than 10 minutes" for files that may be removed on the Packagist servers, per #470 (comment). |
|
This should not happen anymore now, it was a race condition between mirrors but I put a fallback in place now so they should go fetch the missing file if a race happens. Please do tell if you see it again. |
|
Hi, @Seldaek we are still facing the same issue upon running |
|
Same issue here. The "http://packagist.org/p/symfony/process%24ac4ca6b027eeff047d0e37f31208a8d978b98da6c16989614914a639e632ca84.json" file could not be downloaded: failed to open stream: Connection timed out |
|
Issue popped up again, overnight. Here's the trace(s) this time: New Project: Exiting Project: Happens on any new Laravel project and any call to Composer/Packagist on existing ones. Also may be a different url per-project. Not a very helpful string of numbers/letters for the url. Also WaybackMachine has no record for this. So I'm stuck here. @Seldaek letting you know because of #940 (comment) |
|
@Seldaek I am also experiencing this a lot today. e.g. https://drone.owncloud.com/owncloud/core/18699 and pick any of the red jobs. and the errors have various different I am guessing that there is some problem with packagist server(s) somewhere? Is there a status page or twitter thread or... where real-time status of the packagist servers is posted? And how are we supposed to report this sort of error? which is probably a real-time packagist mirror/server sysadmin problem not a packagist software bug. |
|
Hey, sorry looks like one of the mirror nodes failed to sync properly after I did some updates yesterday.. Should be fixed now. |
Because otherwise we are left trying to report via the bug-reporting mechanism on GitHub, and that is not the ideal way to report system-network problems. |
|
Hello, I recently encountered the same following error when trying to composer require seostats/seostats package. Then tried a composer clear-cache Can anybody explain why this is happening? Here is my composer diagnose results |
|
This is happening again, seems to affect Wikimedia CI consistently in each job for the past 20 minutes. |
|
@Krinkle did it get resolved? I messed something up and we had delays in processing metadata updates last night. |
|
@Seldaek that seems to have disappeared now (our task https://phabricator.wikimedia.org/T233264 ). I guess we should really look at setting up a packagist mirror for CI purposes. |
|
Thanks @Seldaek! All green now. |
|
@Seldaek It would appear the issue is back as of a few hours ago. Affects about 1/10 CI builds. |
|
I am also seeing this sort of thing: e.g. https://drone.owncloud.com/owncloud/files_texteditor/452/1/2 I had lots of these errors in overnight jobs. |
|
So
|
|
Hi, im having the same problem with composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition . |
This comment has been minimized.
This comment has been minimized.
|
I've had this issue for several days now, might be one of the mirrors because it works randomly if I just keep doing it over 30 mins or so; [Composer\Downloader\TransportException] |
|
Is there a way to get around this? |
|
This mirror works for me: https://packagist.phpcomposer.com use: and/or add to your repository section in composer.json |
|
that worked ! thanks a lot! where did you find that extra mirror? |
|
You shouldn't use a mirror you don't know. |
@bcastagna It is at least known from packagist: see https://packagist.org/mirrors |
|
This is back today: running with latest version: |
|
[Composer\Downloader\TransportException] using last version |
|
Same here @Seldaek whattup? |
|
@Seldaek Seemed to be back again today, I also had this last week as @ptrm04 reported. Any idea what is causing this? It's interrupting our services pretty hard (Its functioning now, but we were updating some websites this morning and all 200 of them failed due to this error). The "https://packagist.org/p/provider-2017%240e110647cae1251cc87614228c5ee5ac1c4d69290931bf25b9633b9cb61b389c.json" file could not be downloaded (HTTP/1.1 404 Not Found) |
|
I saw this problem also last night and today. I forgot where to find this closed issue! And I raised composer/composer#9112 Is it possible to have somewhere that we can report packagist "run-time-production" issues that are not code bugs? |
|
Can you please do a ping packagist.org or something and let me know which IP it resolves to for you (from the machine experiencing the issue)? |
|
Hi @Seldaek, Here you go: |
|
It's a bit tricky. The CI systems are a number of drone agents in a data center. They start as they are required, no chance to "login" to them and do ordinary commands. Locally at my desk I am seeing both 139.99.120.115 and 51.79.162.48 - I did I don't know how to reproduce it, because sometimes today I got success on a whole set of CI pipelines, and other times there were up to a dozen pipelines that failed like this. |
|
Ok found the problem I think, hopefully you can confirm it is back to normal now. |
|
Hi @Seldaek, I am still experiencing these issues `Installation failed, reverting ./composer.json to its original content. [Composer\Downloader\TransportException] ` (this error was ~2 min ago) Ping output: |
|
Ah yeah sorry a couple more nodes were having the same issue, I rejoiced too quickly, checked all of them now.. |
|
@Seldaek Seems resolved, thanks! |
|
@dilshandesh that seems unrelated, please don't pile up random stuff in this old issue, rather open a new one if you have an issue you can reliably reproduce. |
This one also the same issue which people have faced up there. and I solved it. Thanks! |
|
@dilshandesh The issue reported here was HTTP status code 404. Yours is reporting HTTP status code 500 with a different message. |
|
Wonder how many production workloads this broke / is breaking that are based on the public packagist - private packagist to the rescue? Or are there issues too? |
|
Still ongoing... @Seldaek can you please help |
|
Moved on from 404 to 302 now: |
|
@ptrm04 maybe try using composer 2 preview with |
|
@ptrm04 You can also run your own mirror if packagist.org is too unstable, see https://github.com/Webysther/packagist-mirror |
|
Thanks guys. Also, why on Earth would it want to install "polyfill-php56" - I've searched the entire solution (including vendors) but "polyfill-php56" was not found anywhere. Symfony 5.1 and composer 1.10.10. Are any of you getting those? I want to work on a project but heck can't get it to run due to all these errors. |
Please how did you fix? |
|
Hello! We are starting to experience this 404 issue in our pipelines, when trying to install phpunit 8.5 via simple-phpunit. After a few retries it works, and I'm wondering if not finding the provider json file is due to it expiring sooner than expected. |
|
Hello, today we also see this error in our pipelines. And it also works after few retries. |
|
I encounter the same issue. This is something related to the packagist servers/load balancers. For ex if you try to access a package json directly from the browser (ex: https://repo.packagist.org/p/drupal/libraries.json). If you hit a couple of times Ctrl+F5 (or Cmd+F5) force reload sometimes you get the json sometimes you get 404. |
|
@cslevy this is an issue with v1 metadata not handling deletions very cleanly. Composer 2 correctly does not list that package anymore. |
|
To anyone using github, while using PATs and stepping into this problem for instance during a |
|
[Composer\Downloader\TransportException] Currently happening again (indirectly on Satis 1.0.0). |


Filing a separate issue following from #470, given this is not related to SlowTimer.
This still happens on a regular basis in Wikimedia CI pipeline. Is there a way in which we can prevent this issue in a more general way, that hopefully also avoids too much load or storage pressure on your side?
See https://phabricator.wikimedia.org/P7484$1052 for a recent transcript of a build in which this error occurred.
For that build, it seems like the failure was printed only 4 seconds after the
composer requirecommand.Also:
The text was updated successfully, but these errors were encountered: