Use yarn registry for tarball downloads #206
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Over the weekend, npm have made some changes to the way they serve registry data, ref. https://status.npmjs.org/incidents/t3j62lxb7jg3. This seems to have had an effect on nRF Connect, because downloading app tarballs now fail with a 503 status code.
I have done some debugging, and it seems to happen only when accessing the npm registry through the Electron net API. The Node.js https module works as expected, and accessing the registry through a normal web browser also works. We need to investigate a bit more to pinpoint the issue.
Yarn's registry URL still works fine when accessed from nRF Connect. The tarballs are available from there as well, so we can replace registry.npmjs.org with registry.yarnpkg.com, at least as a short-term fix.