Closed mmellin closed 8 months ago
Ok, after all that it turns out to be if the value is non-existent or not executable, then you have this issue. I guess that's a bit of a "duh" moment.
The fix was to add execution permissions to .apko/range.sh
created by rules_apko
.
$ stat -f '%A %a %N' ./.apko/range.sh
644 1697832095 ./.apko/range.sh
$ chmod u+x .apko/range.sh
$ stat -f '%A %a %N' ./.apko/range.sh
744 1697832095 ./.apko/range.sh
$ bazel info; echo $?
...truncated...
0
cc @tjgq
Overview
Including the flag
--credential_helper=
with nearly any value seems to cause Bazelisk to crash and exit with code 37.This stems from me trying out the new rules_apko ruleset and found that their requirement of using
--credential_helper=
statements in the.bazelrc
files seems to break Bazelisk.Their generated
.apko/.bazelrc
:I tried simply using only the
common --credential_helpers=<value>
in my main.bazelrc
and I get the same behavior. Removing them solved the problem.I found this line from https://github.com/bazelbuild/proposals/blob/main/designs/2022-06-07-bazel-credential-helpers.md which might help explain:
Questions
--credentials_helper=
value that can be used to fix this problem?Environment
WORKSPACE + MODULE.bazel with
common --enable_bzlmod
.Bazelisk installed as Bazel.
Rules_apko v0.2.3.
I see the same behavior on Mac and Ubuntu 20.04 with same bazelisk. Also tried with Bazel 6.4.0 with same outcome.