[rush] Add a --network-concurrency option for troubleshooting network issues #770
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.
People have occasionally been reporting "integrity checksum failed" errors during PNPM install, which result from an ECONNRESET error that seems to be related to an issue with the network connection pool. (See pnpm/pnpm#1230 for details.)
We found that specifying PNPM's
--network-concurrency 1
option eliminates the error (but increases install times). This PR exposes this switch torush install
so we can use it as a workaround. We will experiment with different values and perhaps propose applying a default maximum for the PNPM tool.