-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Crash with empty value of --repo_env #15430
Comments
Seems like the underlying library started refusing null entries while the code relies on them to encode the case where no value is passed and the real value must be taken from the environment. |
Oh, it seems my report lacks the most important part: the actual You can change the command line to I had to deep clean everything before reproducing again:
|
Fixed by ed886ee |
Description of the bug:
When a --repo_env var lacks the value part, Bazel crashes instead of using the value of that variable from the environment.
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Create a trivial repository_rule that uses the env variable.
Which operating system are you running Bazel on?
Linux (NixOS)
What is the output of
bazel info release
?release 5.1.1- (@Non-Git)
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.Bazel 5.1.1, built with nix, on NixOS.
Not tested yet if this is nix/nixos specific.
What's the output of
git remote get-url origin; git rev-parse master; git rev-parse HEAD
?Have you found anything relevant by searching the web?
Seems like the feature is used to be broken: #12886
See also #8869
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: