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
"Command not found" error when running sl too soon after opening a codespace
After opening a new codespace and running the setup.sh script, running the sl command too soon results in a "command not found" error. This happens because the environment variables are not yet fully set.
How to reproduce
Open a new codespace.
Immediately run the sl command:
sl
Expected Result
The sl command should run successfully.
Actual Result
The terminal returns a "command not found" error.
Additional context
This issue occurs because the sl command is run before the environment variables are fully applied. To prevent this, please wait a sufficient amount of time before running the command. If the issue has already occurred, try the following method:
source~/.bashrc
sl
The text was updated successfully, but these errors were encountered:
"Issue might be caused by user error, but I wanted to document it as I continue to learn. I will also try to create a pull request for this issue later, but unfortunately, I can't do more at the moment."
Summary
"Command not found" error when running
sl
too soon after opening a codespaceAfter opening a new codespace and running the
setup.sh
script, running thesl
command too soon results in a "command not found" error. This happens because the environment variables are not yet fully set.How to reproduce
Expected Result
The
sl
command should run successfully.Actual Result
The terminal returns a "command not found" error.
Additional context
This issue occurs because the
sl
command is run before the environment variables are fully applied. To prevent this, please wait a sufficient amount of time before running the command. If the issue has already occurred, try the following method:The text was updated successfully, but these errors were encountered: