Yarn fails getting a package from an artifactory server. or from disk.

[ukilon-okta]

Do you want to request a feature or report a bug?

bug

What is the current behavior?
As a part of a maven build, the error I am getting is:

An unexpected error occurred: "https://artifacts.example.com/artifactory/api/npm/npm-okta-master/grunt-contrib-jasmine/-/grunt-contrib-jasmine-1.0.3.tgz: ENOENT: no such file or directory, open '/root/.cache/yarn/npm-grunt-contrib-jasmine-1.0.3-1915711364755242e038b3ea778946cb5929c6ce/.yarn-tarball.tgz'".

Different random modules fails on different runs - this is not about a specific module.
It's unclear to me if it can't read from the disk or is the server returning a corrupt file.
It would be nice to be able to more verbose logs (in npm we could config loglevel=http)

I don't think this is a yarn bug, but the error message is not very helpful and it would be nice to have a clearer error message.

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?

Please mention your node.js, yarn and operating system version.

• node version: v5.6.0
• yarn v0.17.9
• CentOS 7

[ukilon-okta]

Digging a bit more, the cause for this was running multiple parallel yarn commands (#683). It would still be nice to have more meaningful error messages, as this issue wasn't easy to troubleshoot.