[0.17.0] Error chmod-ing .bin files on 'yarn install'

[dbashford]

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

What is the current behavior?
Running large install after updating to 0.17.0, yarn erroring out at random times in the build running chmod on .bin files. This works on 0.16.1

1st run

[3/4] 🔗 Linking dependencies...
error An unexpected error occurred: "ENOENT: no such file or directory, chmod 'PATH/project/node_modules/.bin/esparse'".

2nd run

[3/4] 🔗 Linking dependencies...
error An unexpected error occurred: "ENOENT: no such file or directory, chmod 'PATH/project/node_modules/.bin/rimraf'".

3rd run

[3/4] 🔗 Linking dependencies...
error An unexpected error occurred: "ENOENT: no such file or directory, chmod 'PATH/project/node_modules/.bin/rimraf'".

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

Just running yarn on large project after cleaning out all the node_modules.

What is the expected behavior?
Not erroring out

Please mention your node.js, yarn and operating system version.
v6.3.1
0.17.0
El Capitan

[moliver-bb]

seeing the same issue on v0.17, was previously working on v0.16.1. Can post my error log if it helps. thanks!

[pmoleri]

Same issue in Windows 10 using bash console. Also working ok in v0.16.1.

[sejoker]

same issue
Please mention your node.js, yarn and operating system version.
v4.6.0
0.17.0
ubuntu 16.04 LTS

[innoist]

Same Issue
node: 7.1.0
yarn: 0.17.0
windows 10

working fine with 0.16.1

[joonki34]

Same Issue
node: 6.9.1
yarn: 0.17.0
windows 10

[jbruni]

Same Issue
node: 6.7.0
yarn: 0.17.0
Lubuntu 15.10 (Virtual Box guest, inside Windows 10 host)

[ingro]

Same errore here:

node: 6.7.0
yarn: 0.17.0
windows 10

[bestander]

We have chmod used only in one place in https://github.com/yarnpkg/yarn/blob/master/src/package-linker.js#L31, this did not change since 0.16.1

[joyfulelement]

We have also noticed the same issue with 0.17.0 reporting error An unexpected error occurred: "ENOENT: no such file or directory, chmod '/node_modules/.bin/semver'". with node version v5.3.0.

[bestander]

I can't reproduce this.
Could anyone show a package.json where it happens?

[pmoleri]

Hi @bestander ,

You can use this steps to reproduce the bug:

npm install -g yarn@0.17.0
git clone https://github.com/yarnpkg/yarn.git yarn-test
cd yarn-test
yarn install

yarn install v0.17.0
[1/4] Resolving packages...
[2/4] Fetching packages...
warning fsevents@1.0.14: The platform "win32" is incompatible with this module.
info "fsevents@1.0.14" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
error An unexpected error occurred: "ENOENT: no such file or directory, chmod 'C:\\Work\\repos\\yarn-test\\node_modules\\.bin\\mkdirp'".
info If you think this is a bug, please open a bug report with the information provided in "C:\\Work\\repos\\yarn-test\\yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

node: v6.9.1
OS: Windows 10 / bash

[dbashford]

Could be related to #1863?

[bestander]

@dbashford yeah, that could

[bestander]

@pmoleri, I am on Mac and don't get an error like you but I get an unfinished install with a quick flash of error:

bestander-mbp:yarn-test bestander$ ~/work/yarn/artifacts/dist/bin/yarn
yarn install v0.18.0-0
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 📃  Building fresh packages...
[1/2] ⠂ spawn-sync
[2/2] ⠂ fsevents
[-/2] ⠂ waiting...
✨  Done in 30.35s.

I am going to revert the change in #1210.
Can anyone check if applying this #1867 fixes the problem?

[pmoleri]

It works.

I tried this:

cd yarn
git checkout v0.17.0
git checkout -b test-fix
npm run build
npm link
yarn -V
> 0.17.0

cd ../yarn-test
yarn install
> error An unexpected error occurred: "ENOENT: no such file or directory, chmod 'C:\\repos\\yarn-test\\node_modules\\.bin\\mkdirp'".

cd ../yarn
git pull https://github.com/bestander/yarn.git fix-nested-bins
npm run build

cd ../yarn-test
yarn install
> Done in 34.47s.

[bestander]

Ok, I'll merge it and make a 0.17.1 in a couple of hours

On Tue, 15 Nov 2016 at 20:07, pmoleri notifications@github.com wrote:

It works.

I tried this:

cd yarn
git checkout v0.17.0
git checkout -v test-fix
npm run build
npm link
yarn -V

0.17.0

cd ../yarn-test
yarn install

error An unexpected error occurred: "ENOENT: no such file or directory, chmod 'C:\repos\yarn-test\node_modules.bin\mkdirp'".

cd ../yarn
git pull https://github.com/bestander/yarn.git fix-nested-bins
npm run build

cd ../yarn-test
yarn install

Done in 34.47s.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1823 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACBdWLBxdphWMslaU7pXqBMQrqypqM9Iks5q-hDogaJpZM4KxuOp
.

[pmoleri]

Verified, working fine in v0.17.2

[webia1]

today same error with:

Yarn version:
0.17.9

Node version:
6.8.1

Platform:
win32 x64

[francisoud]

Same error with:

• Yarn version: 0.21.3
• Node version: 6.9.1
• Platform: win32 x64

I uploaded yarn-error-1823.log in a gist so you can get full log/package.json content...

Running it again, it pass...

[gkaran]

Having the same problem with @francisoud and have tried both 0.22.0 and 0.26.1

• Yarn version: 0.22.0 or 0.26.1
• Node version: 7.0.0
• Platform: win32 x64

Some builds pass while most fail.

[MathieuDoyon]

Same here after I ran yarn cache clean

• Yarn version : 0.21.3
• Node version: 8.1.2
• Platform: macOS Sierra 10.12.5