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

failed writing body #154

Closed
thernstig opened this issue Apr 19, 2021 · 8 comments
Closed

failed writing body #154

thernstig opened this issue Apr 19, 2021 · 8 comments
Labels
bug Something isn't working

Comments

@thernstig
Copy link

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 jorgebucaran/fisher#672).

~/code> fisher install jorgebucaran/nvm.fish
fisher install version 4.3.0
Fetching https://codeload.github.com/jorgebucaran/nvm.fish/tar.gz/HEAD
Installing jorgebucaran/nvm.fish
           /home/userA/.config/fish/functions/_nvm_index_update.fish
           /home/userA/.config/fish/functions/_nvm_list.fish
           /home/userA/.config/fish/functions/_nvm_version_activate.fish
           /home/userA/.config/fish/functions/_nvm_version_deactivate.fish
           /home/userA/.config/fish/functions/nvm.fish
           /home/userA/.config/fish/conf.d/nvm.fish
           /home/userA/.config/fish/completions/nvm.fish
Downloading the Node distribution index for the first time...
(23) Failed writing body
Installed 1 plugin/s
~/code> fisher --version
fisher, version 4.3.0

I am on Ubuntu 20.04.

@jorgebucaran jorgebucaran added the bug Something isn't working label Apr 19, 2021
@meadowsys
Copy link

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

@jorgebucaran
Copy link
Owner

Yes, that's exactly what may be happening sometimes:

command curl --location --silent $mirror/index.tab | command awk -v OFS=\t '
/v0.9.12/ { exit } # Unsupported
NR > 1 {
print $1 (NR == 2 ? " latest" : $10 != "-" ? " lts/" tolower($10) : "")
}
' >$index.temp 2>/dev/null && command mv $index.temp $index && return

I guess this could be solved by downloading the index separately first, then piping the content into the Awk filter.

@Pytal
Copy link

Pytal commented Jun 29, 2021

Will the solution be released?

@jorgebucaran
Copy link
Owner

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.

@aral
Copy link

aral commented Aug 19, 2021

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

@jorgebucaran
Copy link
Owner

Maybe try using this #154 (comment) and see if you can still repro the issue.

@jorgebucaran
Copy link
Owner

Should be fixed in 2.2.6. I hope. 😅

@UsAndRufus
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants