I managed to replicate in our staging environment yesterday, and I'm
retrying today.
This sort of 502 sounds like it could be an issue from GH-side, but it's
unclear why it would happen during the build and not otherwise.
One possible theory is that it's due to a rate limit from GH. If this is
the case, then it's not an easy thing we can fix from our side.
I'll keep an eye on the staging environment, and do build as a small GH
rate limit test
** Changed in: launchpad
Status: New => Triaged
** Changed in: launchpad
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2138851
Title:
npm ERR! Error fetching release: Request failed with status code 502
To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/2138851/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
