yarn add/ yarn fails with ` Assertion `0 && "Unhandled eio response"' failed`

[Ethan-ks]

yarn --version v1.7.0
Do you want to request a feature or report a bug?

Bug report
What is the current behavior?
Running yarn add <package> or simply yarn to install all packages it halts on linking dependencies and fails with the output detailed below.
If the current behavior is a bug, please provide the steps to reproduce.

$ mkdir yarn-test && cd yarn-test
$ yarn init
$ yarn add <package>
OR manually add a dep to package.json and
$ yarn

What is the expected behavior?

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

yarn --version: 1.7.0
node --version: v9.10.0
uname -a: Linux x220 4.16.14_1  x86_64 GNU/Linux Void Linux

Actual behaviour

yarn install v1.7.0
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[-------------------------------------------------------] 0/59node[13989]: ../src/node_file.cc:329:void node::{anonymous}::After(uv_fs_t*): Assertion `0 && "Unhandled eio response"' failed.
 1: node::Abort() [node]
 2: 0x557d5ed55f18 [node]
 3: 0x557d5ed888c0 [node]
 4: uv__work_done [/usr/lib/libuv.so.1]
 5: 0x7f88f5c3d6f4 [/usr/lib/libuv.so.1]
 6: uv__io_poll [/usr/lib/libuv.so.1]
 7: uv_run [/usr/lib/libuv.so.1]
 8: node::Start(uv_loop_s*, int, char const* const*, int, char const* const*) [node]
 9: node::Start(int, char**) [node]
10: __libc_start_main [/usr/lib/libc.so.6]
11: _start [node]
[1]    13989 abort      yarn

[rally25rs]

Looks related to https://bugs.archlinux.org/task/59163

This error comes from the node.js internals for handling filesystem calls. I'm guessing there has to be something specific to node or your OS causing this, and not something in yarn. yarn install certainly isn't broken for everyone or there would be a ton of issues filed.

I doubt there is anything we can do to resolve this from yarn.

[artjomsimon]

Can confirm that (re)installing nodejs-lts-carbon on Arch Linux fixes it, the package got updated.
Seems to be an Arch specific issue after an update to libuv rolled out.

Thx @rally25rs for pointing that out

[mkastner]

Just happened to me on FreeBSD 11.2

yarn global v1.7.0                                                                                                                      │
[1/4] Resolving packages...                                                                                                             │
warning pm2 > [email protected]: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)                                         │
[2/4] Fetching packages...                                                                                                              │
info [email protected]: The platform "freebsd" is incompatible with this module.                                                           │
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.                         │
[3/4] Linking dependencies...                                                                                                           │
[---------------------------------------------------------------------------------------------------------------------------------------│
-----] 0/4751/usr/local/bin/node[45227]: ../src/node_file.cc:354:void node::(anonymous namespace)::After(uv_fs_t *): Assertion `0 && "Un│
handled eio response"' failed.                                                                                                          │
 1: node::Abort(void) [/usr/local/bin/node]                                                                                             │
 2: node::Assert(char const* const[4]*) [/usr/local/bin/node]                                                                           │
 3: void* v8<node::InitFs::Value> node::InitFs(v8::Local<node::InitFs::Object>(v8<node::InitFs::Context>() [/usr/local/bin/node]        │
 4: uv__work_done [/usr/local/lib/libuv.so.1]                                                                                           │
 5: uv__async_stop [/usr/local/lib/libuv.so.1]                                                                                          │
 6: uv__io_poll [/usr/local/lib/libuv.so.1]                                                                                             │
 7: uv_run [/usr/local/lib/libuv.so.1]                                                                                                  │
 8: node::Start(v8::Isolate*, node::IsolateData*, int, char const* const*, int, char const* const) [/usr/local/bin/node]                │
 9: node::Start(uv_loop_s*, int, char const* const*, int, char const* const) [/usr/local/bin/node]                                      │
10: node::Start(int, char**) [/usr/local/bin/node]                                                                                      │
11: _start [/usr/local/bin/node]                                                                                                        │
Abort trap (core dumped)  ]

[davidzambo]

Same happened to me on Debian unstable

[cyberj]

Same here on Debian Sid :

$ node --version
v8.11.2
$ yarn --version
1.7.0
$ uname -a
Linux dagobah 4.16.0-2-amd64 #1 SMP Debian 4.16.16-2 (2018-06-22) x86_64 GNU/Linux

[Ethan-ks]

I uninstalled the node coming from the void package repositories, and replaced it with node installed via nvm. This solved the problem, so it looks like the package for either libuv or node on the void repo (and likely any other affected systems) needs to be updated.

[badosu]

Downgrading libuv on arch to libuv-1.20.2-1-x86_64 fixed the issue to me.

The erroring version was: libuv-1.21.0-1-x86_64

Also had to downgrade nodejs (10.5.0-1 => 9.11.1-1)

[thehowl]

Void Linux here. I fixed it by upgrading libuv to 1.22.0. Probably got fixed in that release.

[KonstantinSimeonov]

Gentoo Linux/node 8.11.3/yarn 1.8.0
Upgrading libuv to 1.22.0 solved it for me.