Closed thernstig closed 2 years ago
I saw this once in a codespace. I didn't save the log cause I thought it was the codespace being funny. I think it's failing to get the node distribution index because I could only install a node version after running nvm list-remote
first
Yes, that's exactly what may be happening sometimes:
I guess this could be solved by downloading the index separately first, then piping the content into the Awk filter.
Will the solution be released?
I've yet to see this issue myself. Maybe try downloading the index and then piping it into the filter and see if you can reproduce the problem. If you can't, then send me PR.
In case it helps, just ran into it too. Seems to have installed otherwise:
❯ nvm install 12.16.2
(23) Failed writing body
Installing Node v12.16.2 lts/erbium
Fetching https://nodejs.org/dist/v12.16.2/node-v12.16.2-linux-x64.tar.gz
Now using Node v12.16.2 (npm 6.14.4) ~/.local/share/nvm/v12.16.2/bin/node
Maybe try using this https://github.com/jorgebucaran/nvm.fish/issues/154#issuecomment-826018435 and see if you can still repro the issue.
Should be fixed in 2.2.6
. I hope. 😅
I'm getting this issue again - not sure it's fixed. Addressed by running mkdir /Users/<username>/.local/share/nvm
. If it makes a difference, I'm using a fresh MBP with M1.
We still get the old
(23) Failed writing body
at times. This time it was found when installing nvm through fisher, but we deducated it was not fisher but actually nvm.fish still containing the problem (see https://github.com/jorgebucaran/fisher/issues/672).I am on Ubuntu 20.04.