you want to report a bug?
If the current behavior is a bug, please provide the steps to reproduce.
I am getting this error whenever I am using the docker-compose up command and then it goes to resolving issues and then gives out some warning and this error. please help
Please mention your node.js, yarn and operating system version.
ubuntu 18.04
yarn 1.13.0
node v8.15.0
i see this often with https://github.com/fabiospampinato/bump from within our Jenkins pipeline
looks like https://github.com/yarnpkg/yarn/issues/4412 was related but the OP closed
when i see this occur, i've tried to load it directly in my browser. when i do, i'm able to start a download of the file, but it eventually gets a "Failed Network" error in Chrome, which I'm guessing is a result of the EOF error
the issue seems intermittent, usually shortly after it works again, but its frustrating when builds fail due to it
Also having this issue in CI
Any updates?
Same here using the latest yarn 1.17.3 in CI.
@imsnif any ideas on temporary solutions or how this might be resolved? it's so frustrating with CI constantly having builds fail because of it 😞
It's also happening for us in Google Cloud Functions builds, for instance:
âš functions[<redacted>(us-central1)]: Deployment error.
Build failed: {"error": {"canonicalCode": "INVALID_ARGUMENT", "errorMessage": "`yarn_install` had stderr output:\nwarning Resolution field \"[email protected]\" is incompatible with requested version \"hoist-non-react-statics@^3.3.0\"\nwarning Resolution field \"[email protected]\" is incompatible with requested version \"hoist-non-react-statics@^3.3.0\"\nwarning Resolution field \"[email protected]\" is incompatible with requested version \"hoist-non-react-statics@^3.3.0\"\nwarning Resolution field \"[email protected]\" is incompatible with requested version \"hoist-non-react-statics@^3.3.0\"\nwarning Resolution field \"[email protected]\" is incompatible with requested version \"hoist-non-react-statics@^2.5.0\"\nerror An unexpected error occurred: \"https://registry.yarnpkg.com/grpc/-/grpc-1.22.2.tgz: unexpected end of file\".\n\nerror: `yarn_install` returned code: 1", "errorType": "InternalError", "errorId": "00D4E024"}}
For clarity, here is the end of the errorMessage
:
error An unexpected error occurred: "https://registry.yarnpkg.com/grpc/-/grpc-1.22.2.tgz: unexpected end of file".
error: `yarn_install` returned code: 1
This is becoming a main blocker during our deployment process 😕
This is happening to me to, it's always the same package and it's a package with a larger binary inside about 4 MB.
This is happening intermittently in our Azure DevOps piplines (running Windows). But I just ran into this running yarn from a Debian 9 installation. Would like to know what would cause this, how to root cause the issue?
Also happens for us frequently in GitLab CI pipelines
@arcanis any chance we can get a little attention here?
it's not an ideal solution but for the time being, I was able to patch my npm dependency directly to the github source.
"@fabiospampinato/bump": "https://github.com/fabiospampinato/bump.git",
Replacing the above pattern with your dependency of course.
Please be warned, this could be a huge tradeoff and might depend on the dependency for being able to do this, as you may lose some abilities to maintain the right version of the dependency and other npm/yarn features.
I encountered this error today. Failed when I retried right after, but worked again when I retried after a couple minutes. Bug in the server running at registry.yarnpkg.com I suppose?
Most helpful comment
It's also happening for us in Google Cloud Functions builds, for instance:
For clarity, here is the end of the
errorMessage
:This is becoming a main blocker during our deployment process 😕