You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We discovered this issue while porting create-react-app over to Azure DevOps build pipeline (facebook/create-react-app#7096). If a connection to the uplink (e.g. registry.npmjs.org) times out, Verdaccio returns a 404 status code, which causes the npm/yarn client to fail.
Expected behavior
Verdaccio should return a 503 status code which tells the npm/yarn client to try again.
🤖This thread has been automatically locked 🔒 since there has not been any recent activity after it was closed.
We lock tickets after 90 days with the idea to encourage you to open a ticket with new fresh data and to provide you better feedback 🤝and better visibility 👀.
If you consider, you can attach this ticket 📨 to the new one as a reference for better context.
Thanks for being a part of the Verdaccio community! 💘
This issue may be related to #720.
Describe the bug
We discovered this issue while porting
create-react-app
over to Azure DevOps build pipeline (facebook/create-react-app#7096). If a connection to the uplink (e.g.registry.npmjs.org
) times out, Verdaccio returns a404
status code, which causes the npm/yarn client to fail.Expected behavior
Verdaccio should return a
503
status code which tells the npm/yarn client to try again.@willsmythe helped us fix this in a fork of his. You can see the diff here: master...willsmythe:fix-404-on-uplink-timeout.
The text was updated successfully, but these errors were encountered: