Audit randomly fails due to 503 (Yarn and NPM)
See original GitHub issueHello,
I am using audit-ci
in my CircleCI workflow (thank you for this package). I have a annoying issue: sometimes, the audit fails with the error:
Invocation of npm audit failed:
npm ERR! code ENOAUDIT
npm ERR! audit Your configured registry (https://registry.npmjs.org/) does not support audit requests.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/circleci/.npm/_logs/2019-04-03T14_57_17_893Z-debug.log
Exiting...
I understand this seems to be an error from NPM server and not audit-ci
itself, however, I never encountered this error while running npm audit
locally on the project.
This error is very random: sometimes it occurs 5 times in a row, sometimes it does not happen for days.
Did some of you stumble upon this issue? Do you know if we can implement some kind of retying mechanism in audit-ci
to circumvent it?
Thank you
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Npm Error: 503 Service Unavailable for npm install command
Seems like your npm registry config pointing to some private registry that is down or unavailable. Try to check npm configuration :
Read more >yarn-audit-fix - npm
Solution. Fortunately, there are several workarounds: Compose npm audit fix with lockfile converter (thanks to Gianfranco P., stackoverflow/ ...
Read more >Troubleshooting Node.js Deploys - Heroku Dev Center
Your Node.js deploy failed - now what? Start with these simple steps to troubleshoot a build issue. Check the buildpack.
Read more >Node.js 502 Bad Gateway Issues and How To Resolve Them
In December of 2018, many Node.js users noticed that their applications randomly returned an HTTP status code 502 “Bad Gateway” error.
Read more >10 best practices to containerize Node.js web applications ...
Are you looking for best practices on how to build Node.js Docker ... setting with the installation of production-related dependencies, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Released in v1.7.0
Just chiming in that we have had this happen multiple times in different projects and different environments/OSs, so it’s definitely a thing. Always gets fixed by rerunning the task so retry mechanism would indeed be a great addition, especially if it just checks if the error is the one mentioned above (“does not support” & “npmjs.org”) -> try again.