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
Commands like garden scan fail with errors like this if there's a broken symlink:
ENOENT: no such file or directory, stat '/Users/eronarn/Code/qf/app/assets/javascripts/docs'
In my case:
[eronarn@ip-192-168-10-243 qf]$ ls -lath '/Users/eronarn/Code/qf/app/assets/javascripts/docs'
lrwxr-xr-x 1 eronarn staff 31 Nov 27 2018 /Users/eronarn/Code/qf/app/assets/javascripts/docs -> ../../../qdocs_build/_static/js
The intervening folders exist, but _static doesn't, so the symlink is (currently) broken.
Expected behavior
Local symlink issues don't prevent non-build commands, like scanning the project.
Suggested solution(s)
There should be a warning about the symlink, or potentially the module may fails building if a critical symlink can't be resolved; but project-level commands shouldn't fail on this condition.
Additional context
Usually one would expect symlinks to resolve, but not always; like in this case where I'm working in a repo where I haven't been building the docs. The application would work without the symlink and it's there for developer convenience.
Your environment
[eronarn@ip-192-168-10-243 qf]$ garden version
0.10.2
The text was updated successfully, but these errors were encountered:
Bug
Current Behavior
Commands like
garden scan
fail with errors like this if there's a broken symlink:ENOENT: no such file or directory, stat '/Users/eronarn/Code/qf/app/assets/javascripts/docs'
In my case:
The intervening folders exist, but
_static
doesn't, so the symlink is (currently) broken.Expected behavior
Local symlink issues don't prevent non-build commands, like scanning the project.
Suggested solution(s)
There should be a warning about the symlink, or potentially the module may fails building if a critical symlink can't be resolved; but project-level commands shouldn't fail on this condition.
Additional context
Usually one would expect symlinks to resolve, but not always; like in this case where I'm working in a repo where I haven't been building the docs. The application would work without the symlink and it's there for developer convenience.
Your environment
The text was updated successfully, but these errors were encountered: