hiqdev / asset-packagist

Asset Packagist
https://asset-packagist.org
BSD 3-Clause "New" or "Revised" License
247 stars 25 forks source link

TransportException file not found #106

Closed kporras07 closed 5 years ago

kporras07 commented 5 years ago

Hi there,

I'm having issues like this in my CI. Is this somehow related to yesterday's issues with storage? Is it possible to workaround it?

[Composer\Downloader\TransportException]                                                                                                                                          
  The "https://asset-packagist.org/p/npm-asset/byline/920da2ad7002a68fa527d3d93088f3a7484ba8e264f0a9d08789092bb8f6e3b7.json" file could not be downloaded (HTTP/1.1 404 Not Found)  

It sometimes change to querystring or querystring-es3 but the error is the same; the hash provided by provider-latest can't be fetched.

Any ideas/help?

Thanks,

socialnicheguru commented 5 years ago

https://github.com/composer/packagist/issues/1042 I am getting the same with random packages.

I run "composer update" package files are not found. And it is not the same package.

Screen Shot 2019-10-28 at 9 52 47 AM

I run composer clearcache and then composer update again and I get the same thing.

When I take a look at the packages there are so many where Commit SHA is not defined.

Screen Shot 2019-10-29 at 7 47 45 AM
tigrasti commented 5 years ago

Same here

socialnicheguru commented 5 years ago

also the unrecognized packages seem to change

jasonhuvl commented 5 years ago

Same issue

[Composer\Downloader\TransportException] The "https://asset-packagist.org/p/npm-asset/require-package-name/f7efe92420d1470aa98a5741f575405edf8092217762c6e33972c234d381d0e6.json" file could not be downloaded (HTTP/1.1 404 Not Found)

socialnicheguru commented 5 years ago

now i get this and I cannot find "npm-asset/randy.js"

[Composer\Downloader\TransportException]
The "https://asset-packagist.org/p/npm-asset/randy.js/a32c86adb58411baee0944e539085d45fb8ae8489c7fe8fbdb2b5991b7407b60.json" file could not be downloaded (HTTP/1.1 404 Not Found)

SilverFire commented 5 years ago

We are running full packages upgrade, all packages that are not available now will be loaded&updated during the next few hours.

I will keep you updated, guys.

rodrigoaguilera commented 5 years ago

I just want to say thank you for the service you offer for free to the community. Please take the time is necessary to fix the issues.

socialnicheguru commented 5 years ago

@SilverFire You guys are amazing! thank you!

kporras07 commented 5 years ago

Yep, thank you very much for all the hard work :D

socialnicheguru commented 5 years ago

@SilverFire, Will you be making an announcement in this queue or on the project page? It's 8:30am pst and there are still issues with the repositories:

[Composer\Repository\RepositorySecurityException]
The contents of https://asset-packagist.org/p/npm-asset/is-integer/6b2910b9e76ac61efac57d3dc73a8f6cd7381428055d8
218dbc13e2a51654a72.json do not match its signature. This could indicate a man-in-the-middle attack or e.g. anti
virus software corrupting files. Try running composer again and report this if you think it is a mistake.

I just want to know when I can come back in and try again/test.

SilverFire commented 5 years ago

Gave a detailed reply to a neighbor issue. Please, check it out: https://github.com/hiqdev/asset-packagist/issues/105#issuecomment-548221699

SilverFire commented 5 years ago

Closing this issue for now. Thanks!

Thanty commented 5 years ago

@SilverFire I'm really sorry but problem still exists.

[Composer\Repository\RepositorySecurityException] The contents of https://asset-packagist.org/p/npm-asset/get-imports/67f5d292c49a427cdc355a26cc8207353282752447ba2ebfa474769aad1cdf18.json do not match its signature. This could indicate a man-in-the-middle attack or e.g. antivirus software corrupting files. Try running composer again and report this if you think it is a mistake.

Fetching all used repositories didn't help.

socialnicheguru commented 5 years ago

Please allow others to confirm before closing. This is not fixed. There are two issues: content mismatch which I do believe was fixed (and was not my issue in the first place).

The other is missing packages which is still going on. I will open another issue to make sure that it gets the attention it deserves

SilverFire commented 5 years ago

Moving discussion to #108