--credential_helper: overly verbose error messages when a credential is missing #23473
Labels
P2
We'll consider working on this in future. (Assignee optional)
team-Remote-Exec
Issues and PRs for the Execution (Remote) team
type: bug
Description of the bug:
When authenticating to a remote cluster with the
--credential_helper
flag, if the credential is expired or unavailable, Bazel's error message is very long and confusing:In this case, the credential helper exits with a non-zero exit code and prints this message on stderr:
It looks like Bazel is attempting multiple gRPC calls, both to
Capabilities
and toPublishBuildEvent
.Bazel also exits with code 34, a remote error, which doesn't seem correct.
I think ideally Bazel should invoke the credential helper early when starting up, and if that fails, exit with a short message echoing the stderr output from the credential helper. Bazel shouldn't attempt to call gRPC services if it failed to obtain a credential.
Which category does this issue belong to?
Remote Execution
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Install any credential helper. We're testing this with
engflow_auth
. But a script that exits non-zero and prints anything on stderr would work.Build any target with:
Which operating system are you running Bazel on?
macOS
What is the output of
bazel info release
?release 8.0.0-pre.20240730.1
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.n/a
What's the output of
git remote get-url origin; git rev-parse HEAD
?If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.
n/a
Have you found anything relevant by searching the web?
n/a
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: