Do you want to request a feature or report a bug?
What is the current behavior?
yarn install quits silently if fetching one of the packages times out during fetch phase due to package size and/or network lag.
- yarn does quit before reaching linking phase, therefore no packages are installed
- No error message
- Return code 0
(Shortened) example output:
$ yarn install --verbose yarn install v1.5.1 [...] [1/4] Resolving packages... warning: [...] [2/4] Fetching packages... verbose 1.45 Performing "GET" request to "https://registry.yarnpkg.com/envfile/-/envfile-2.3.0.tgz". [...] verbose 20.696 Performing "GET" request to "https://registry.yarnpkg.com/command-exists/-/command-exists-1.2.2.tgz". $
If the current behavior is a bug, please provide the steps to reproduce.
git clone https://github.com/theia-ide/theia-apps
mv next.package.json package.json
(Retry until it fails, maybe use slow internet connection)
The large package here is
@theia/java, which clocks in at around 33MB.
What is the expected behavior?
yarn install prints an error message with the timeout, the package name and url it failed to fetch. Finally, it quits with a return code
Please mention your node.js, yarn and operating system version.
- OS: docker image
- (Host: Ubuntu
Maybe related: #5055
--network-timeout nor setting
--mutex network helped. Interestingly, the
yarn install quits long before the network timeout is due (e.g., timeout 60000ms,
yarn install quits after 35s).
I noticed that in the cases where it fails locally (via
docker run ...), my system monitor shows a very slow download (~150Kb/s on a 50 Mb/s connection). The other runs go with ~5 Mb/s).