Skip to content
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

config doesn't error on duplicate --define values #14760

Closed

Conversation

illicitonion
Copy link
Contributor

When --define flags are interpreted by other commands, the last one
wins. Currently bazel config causes a server crash when interpreting
duplicate --define values.

This change makes config consistent with the other commands, and
re-uses the same deduplication code across all call-sites.

When `--define` flags are interpreted by other commands, the last one
wins. Currently `bazel config` causes a server crash when interpreting
duplicate `--define` values.

This change makes `config` consistent with the other commands, and
re-uses the same deduplication code across all call-sites.
@katre katre self-requested a review February 8, 2022 19:29
Copy link
Member

@katre katre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, I'll get this merged once the tests pass.

@bazel-io bazel-io closed this in 7a65271 Feb 8, 2022
@illicitonion illicitonion deleted the config-duplicate-defines branch February 8, 2022 20:57
illicitonion added a commit to illicitonion/bazel that referenced this pull request Feb 8, 2022
When `--define` flags are interpreted by other commands, the last one
wins. Currently `bazel config` causes a server crash when interpreting
duplicate `--define` values.

This change makes `config` consistent with the other commands, and
re-uses the same deduplication code across all call-sites.

Closes bazelbuild#14760.

PiperOrigin-RevId: 427266039
@illicitonion
Copy link
Contributor Author

@bazel-io fork 5.2

1 similar comment
@keith
Copy link
Member

keith commented Apr 1, 2022

@bazel-io fork 5.2

@illicitonion
Copy link
Contributor Author

@bazel-io flag

@bazel-io bazel-io added the potential release blocker Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone label Apr 4, 2022
@ckolli5
Copy link

ckolli5 commented Apr 13, 2022

@bazel-io fork 5.2.0

@bazel-io bazel-io removed the potential release blocker Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone label Apr 13, 2022
ckolli5 added a commit that referenced this pull request May 12, 2022
When `--define` flags are interpreted by other commands, the last one
wins. Currently `bazel config` causes a server crash when interpreting
duplicate `--define` values.

This change makes `config` consistent with the other commands, and
re-uses the same deduplication code across all call-sites.

Closes #14760.

PiperOrigin-RevId: 427266039

Co-authored-by: Daniel Wagner-Hall <dwagnerhall@apple.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants