-
Notifications
You must be signed in to change notification settings - Fork 5
--outdir .
flag value makes furyctl not working correctly
#508
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
May be related to #434 |
Kinda related but not, they not share the same root cause. The issue is that furyctl when launches the tools, sometimes changes the working directory from where it launches them. So the relative path set in the outdir does not point to the right place anymore. This issue is even more evident if you launch furyctl using the Passing We need to convert the outDir to an absolute path early to fix this issue. Exactly the same issue is present with the |
- Improve management of relative paths, calculating them once. - Set outdir globally and reuse. - Reduce code duplication (still lots to improve) - Move flags processing to helper func when present - Improve UX on some error messages, help messages and debug messages - Normalize words in help messages Fixes #508
- Improve management of relative paths, calculating them once. - Set outdir globally and reuse. - Reduce code duplication (still lots to improve) - Move flags processing to helper func when present - Improve UX on some error messages, help messages and debug messages - Normalize words in help messages Fixes #508
Uh oh!
There was an error while loading. Please reload this page.
When
--outdir
value is.
furyctl cannot find binaries.Temporary fix:
--outdir $PWD
The text was updated successfully, but these errors were encountered: