Abdirahim Musse

@stefanoeb I also experienced this issue and found that it is caused by this issue https://npm.community/t/npm-ci-produces-a-tonn-of-excess-warnings-on-install/3261. This can be fixed by upgrading the nodejs image used in the docker file....

@noviicee I've been busy with other tasks lately. Feel free to give this a go! Thanks!

Update PR is now Open https://github.com/RuntimeTools/appmetrics/pull/538

@bnoordhuis I agree the right way is to make libuv handle it. 1) To my understanding libuv needs to get updated to handle EUNATCH so that the error code can...

@bnoordhuis I've landed a PR to add `EUNATCH` support in libuv.

@bnoordhuis @mhdawson @richardlau We can now use error.code to refer to EUNATCH in node versions that use libuv 1.46.0. I've updated the checks to look for `EADDRNOTAVAIL` or `EUNATCH` CC...

Ping @bnoordhuis Can you please re-review the latest changes?

Hey @bnoordhuis 👋🏿 This is PR is still needed as libuv now has support for the `EUNATCH` errno. The libuv changes: https://github.com/libuv/libuv/pull/4047 We are not remapping EUNATCH -> ECONNREFUSED. Before...

@mhdawson Yes I've addressed Kevin's comments in https://github.com/nodejs/node/pull/48050/commits/f83b1021341d5e9ddc3ea5e590d947e4e85d5703

I started to investigate this issue last week. I asked @mhdawson to spin up some stress tests ref: https://ci.nodejs.org/job/node-stress-single-test/nodes=rhel8-ppc64le/469/console We ran this test case 1000 times on rhel8 ppc64le. This...