Fix invoke.sh not detecting symlinks #6731
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
When invoke.sh is executed using a symlink with a working directory outside of InvokeAI's root directory, it will fail with the following message:
<path to symlink>: line 23: .venv/bin/activate: No such file or directory
invoke.sh attempts to cd into the correct directory at the start of the script, but will cd into the directory of the symlink instead. This MR fixes that.
QA Instructions
I performed these checks on Arch Linux 6.10.3-arch1-2 (64-bit). I did not test this MR on other Linux distributions or MacOS but to my knowledge
readlink
is available there as well by default.Additional Notes
A similar fix may be needed for invoke.bat. I don't have a windows machine and don't know batch well enough to be sure though.
Checklist