Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Yarn 1.22.8 preinstall script fails on GitHub actions with bad file descriptor number #8360

Closed
agrobbin opened this issue Sep 28, 2020 · 7 comments

Comments

@agrobbin
Copy link

Bug description

When Yarn 1.22.8 hit the NPM registry, GitHub Actions started installing it when running npm install -g yarn, and we started seeing failures.

Command

> [email protected] preinstall /opt/hostedtoolcache/node/12.16.3/x64/lib/node_modules/yarn
> :; (node ./preinstall.js >& /dev/null || true)

sh: 1: Syntax error: Bad fd number
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! [email protected] preinstall: `:; (node ./preinstall.js >& /dev/null || true)`
npm ERR! Exit status 2
npm ERR! 
npm ERR! Failed at the [email protected] preinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

What is the current behavior?
npm install -g yarn fails when running the preinstall script.

What is the expected behavior?
npm install -g yarn successfully runs the preinstall script.

Steps to Reproduce

  1. npm install -g yarn

Environment

  • Node Version: 12.16.3
  • Yarn v1 Version: 1.22.8
  • OS and version: Ubuntu 18.04.5 LTS
@alexbikazzan
Copy link

We had the same problem on our build server inside a docker container. We had to run npm install -g [email protected] and it worked, so I guess there is something in the latest version.

@gonzaloaune
Copy link

Seems it's fixed now

@jorrit91
Copy link

@gonzaloaune Can confirm, seems to be fixed.

@laander
Copy link

laander commented Sep 28, 2020

We're still experiencing the issue with the latest version (as of writing) v1.22.9. Seems fishy since latest tag in this repo is v1.22.5 - where does the latest 4 patch versions come from?

@ClemArt
Copy link

ClemArt commented Sep 28, 2020

Resolved with the 1.22.10.
Just as @laander asked, where does the last 5 patch come from ? Are they released from specific commits ?

@alexbikazzan
Copy link

They are tracked on npm:
https://www.npmjs.com/package/yarn

Maybe just not tagged on github I guess?

@arcanis
Copy link
Member

arcanis commented Sep 28, 2020

Going to close as duplicate of #8358, which has more details (basically, the tags don't reflect at the moment the releases due to an infra problem. Those commits were published on the 1.22-stable branch.).

@arcanis arcanis closed this as completed Sep 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants