-
Notifications
You must be signed in to change notification settings - Fork 730
[Bug] #138
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
"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." |
Fixes skills#138 - Added a note advising users to wait sufficiently if errors occur. - Note: Running commands before the codespace is fully set up might result in errors. If an error occurs, please open a new codespace and wait a sufficient amount of time before trying again.
@jhonatanparada499 |
@iriru Thank you for raising this issue! I'll get this triaged for review ✨ Our team will provide feedback regarding the best next steps for this issue - thanks for your patience! 💛 |
@nguyenalex836 I found that updating the postCreateCommand helps solve the issue, can you please review this PR and merge if it looks good? #160 |
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: