You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know that using "weird results" in a title is a sign you're about to get the worst issue report ever, but let me output what I run into and we can judge from there.
When running asdf install nodejs it would fail to download:
> asdf install nodejs
Trying to update node-build... ok
Downloading node-v14.19.3.tar.gz...
-> https://nodejs.org/dist/v14.19.3/node-v14.19.3.tar.gz
error: failed to download node-v14.19.3.tar.gz
-> https://nodejs.org/dist/v14.19.3/node-v14.19.3.tar.gz
error: failed to download node-v14.19.3.tar.gz
BUILD FAILED (OS X 13.4.1 using node-build 4.9.119)
I was able to download the file with wget. I thought it might be related to #344, but I do not have aria2c in my path.
To try and diagnose the problem, I tried to use ASDF_NODEJS_VERBOSE_INSTALL. I ran the command like:
However, this started to build nodejs from source, as if I had set ASDF_NODEJS_FORCE_COMPILE. I can't paste the results because it was thousands of lines of linking. Here's a snippet:
It took a long long long time, probably because of a mix of building and having to repeatedly flush tons of stuff to stdout.
I was going to post an issue about that. To help with the issue description, I was going to time both of the previous commands to show that asdf install nodejs was probably not building from source while the command with the env var was.
BUT when I ran install with time it worked:
>time asdf install nodejs
Trying to update node-build... ok
Downloading node-v14.19.3.tar.gz...
-> https://nodejs.org/dist/v14.19.3/node-v14.19.3.tar.gz
WARNING: node-v14.19.3 is in LTS Maintenance mode and nearing its end of life.
It only receives *critical* security updates, *critical* bug fixes and documentation updates.
Installing node-v14.19.3...
Installed node-v14.19.3 to /Users/andrewszczepanski/.asdf/installs/nodejs/14.19.3
One idea I had was maybe it has to do with arg parsing. I noticed that asdf-nodejs parse scripts using $1 and $2. However, time doesn't clobber arguments, as shown with this simple test:
>echo"echo \$1"> test_script.sh
> chmod 755 test_script.sh
> ./test_script.sh hello
hello
>time ./test_script.sh hello
hello
./test_script.sh hello 0.00s user 0.01s system 42% cpu 0.022 total
It also wasn't nodejs.org being flaky -- I tried the command a few times and received error: failed to download node-v14.19.3.tar.gz while downloading it in between runs with wget.
Other than that, I'm at a loss as to what it could be. It seems like a major Heisenbug.
I don't really expect anyone to fix this with this information given, but maybe if someone else runs into it they can simply use time to workaround it.
Specs/maybe useful info:
Chip Apple M1 Pro
mac OS 13.4.1 (22F82)
zsh 5.9 (arm-apple-darwin21.3.0)
asdf v0.12.0
On company VPN
The text was updated successfully, but these errors were encountered:
I know that using "weird results" in a title is a sign you're about to get the worst issue report ever, but let me output what I run into and we can judge from there.
When running
asdf install nodejs
it would fail to download:I was able to download the file with
wget
. I thought it might be related to #344, but I do not havearia2c
in my path.To try and diagnose the problem, I tried to use
ASDF_NODEJS_VERBOSE_INSTALL
. I ran the command like:However, this started to build nodejs from source, as if I had set
ASDF_NODEJS_FORCE_COMPILE
. I can't paste the results because it was thousands of lines of linking. Here's a snippet:It took a long long long time, probably because of a mix of building and having to repeatedly flush tons of stuff to stdout.
I was going to post an issue about that. To help with the issue description, I was going to
time
both of the previous commands to show thatasdf install nodejs
was probably not building from source while the command with the env var was.BUT when I ran install with
time
it worked:One idea I had was maybe it has to do with arg parsing. I noticed that asdf-nodejs parse scripts using
$1
and$2
. However,time
doesn't clobber arguments, as shown with this simple test:It also wasn't nodejs.org being flaky -- I tried the command a few times and received
error: failed to download node-v14.19.3.tar.gz
while downloading it in between runs withwget
.Other than that, I'm at a loss as to what it could be. It seems like a major Heisenbug.
I don't really expect anyone to fix this with this information given, but maybe if someone else runs into it they can simply use
time
to workaround it.Specs/maybe useful info:
Chip Apple M1 Pro
mac OS 13.4.1 (22F82)
zsh 5.9 (arm-apple-darwin21.3.0)
asdf v0.12.0
On company VPN
The text was updated successfully, but these errors were encountered: