-
Notifications
You must be signed in to change notification settings - Fork 54
avn could not activate node #47
Comments
@hiimtaylorjones Yep, I did look at it and done everything as described, but nothing helped. Any other ideas? |
The closest environment in which I can attempt to reproduce this has only this change:
Everything's working as expected, though. If you're open to it, the best way to resolve this would be to start adding debugging output to the code (you can edit it right in |
@wbyoung sure, let's debug it. I am actually running it in Docker container, based on |
Start here. That file is pretty small, so if the error is in there, it shouldn't be too hard to understand & track down. You may need to log to a file if nothing shows up using |
@wbyoung Alright. Thanks for the tip. I found the problem. The |
Yeah, both sound smart. Want to send a PR? |
I am not familiar with the internals, however is this a good place where we could check if SHELL is set? avn.sh#L9 |
Yes. |
I know this has been already discussed, but I am still bumping into this:
Details
0.2.3
v6.5.0
0.31.7
GNU bash, version 4.3.30(1)-release (x86_64-pc-linux-gnu)
The output of
__avn_debug
in the directory with a.node-version
file is:avn
is loaded in my~/.bash_profile
file with:nvm specific
nvm
user I am confirming that I did not install with HomebrewThe text was updated successfully, but these errors were encountered: