-
-
Notifications
You must be signed in to change notification settings - Fork 69
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
[BUG] bqm: command not found in load_supported_setups.sh #207
Comments
load_supported_setups: expand aliases to fix bug #207
Should be fixed in the next |
Fixed ? |
@gbe can you check? |
No, with the move to Debian12, it's even worse.
|
I manually changed the relative path to a full path where an error was returned.
|
The bqm issue is fixed in dev. I could successfully test it after the fixes done in #245 |
Not fixed in dev actually. Since the PR is not merged yet the fix doesn't apply to the nightly image. |
We're good it seems, please open again if you feel like the issue is not resolved in the new nightly images |
Describe the bug
When executing the script
/.exegol/load_supported_setups.sh
, the script fails to find the toolbqm
.This is likely due to the change introduced before releasing the images v3.1.0 with the introduction of ruby wrappers.
Calling
bqm
directly from azsh
prompt works as a zsh alias exists. However, the scriptload_supported_setups.sh
is executed bybash
which does not know the alias. Hence, it fails to find the binary.This bug breaks the support of bloodhound for my-resources.
Steps To Reproduce
Exegol Wrapper Version
Exegol container information
Exception
No response
Additional context
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: