Audit randomly fails due to 503 (Yarn and NPM) about audit-ci

[mikkotikkanen]

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.

[quinnturner]

Released in v1.7.0

[quinnturner]

This is very strange indeed! I don't think I have encountered this personally within the audit-ci project's own audits. Can you check npm --version in CircleCI? Perhaps you can run npm i -g npm in CircleCI, fixing some NPM bug?

[clement-escolano]

npm --version gives 6.4.1 which is indeed pretty old. I will update npm and will see if it solves the problem.
Thank you for your input. I will come back to tell if it solved the problem or not.

[quinnturner]

Hi again,

You are not alone on this issue. It has now happened on this project as well and seems to be an issue for others. Note that it is independent of CircleCI as it happened for both of our CircleCI and Travis-CI builds.

At this time, it seems as if the only options for now would be a retry mechanism.

[clement-escolano]

Thank you for the information 😄 Well, it is a good news in a way: it seems that NPM is aware of the issue and working on it.

[djomaa]

Hi.

In my opinion, it would be great to integrate a retry mechanism into audit-ci. What do you think about it?