Open albertocavalcante opened 4 months ago
Actually I've just realized my mistake, I've inadvertently set BAZELISK_HOME
to ~/.bazeliskrc
, that's why it failed.
This is clearly not a bug but bad user behavior. Still I'm planning to open a PR to improve the error message. (In fact I think it can detect a situation when the BAZELISK_HOME matches the rcFileName and prevent it from executing, marking a "forbidden" path). Although it's very unlikely someone will make the same mistake I just did.
I noticed you have your own fork of bazelisk.go
, will leave it open if you think it worth it, otherwise feel free to close it. Thanks.
(will also edit the title)
What happened?
I still may need to re-reproduce and confirm my findings but I'm already sharing it anyway. I'll update this issue accordingly.
The error I'm currently getting:
Standalone Aspect CLI
Bazelisk
Version
Development (host) and target OS/architectures: linux_x86_amd4 (WSL2)
Output of
bazel --version
: Errors outVersion of the Aspect rules, or other relevant rules from your
WORKSPACE
orMODULE.bazel
file: NoneLanguage(s) and/or frameworks involved: None
How to reproduce
Any other information?
(Note: I'm using a fork of bazelisk which carries these changes only: https://github.com/bazelbuild/bazelisk/pull/587, to reproduce it you can change ~ with the actual homedir path).