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

Fix the placement of the pex verbosity args. #15243

Merged
merged 1 commit into from
Apr 25, 2022

Conversation

benjyw
Copy link
Contributor

@benjyw benjyw commented Apr 24, 2022

The pex subcommands mechanism registers the -v flag twice,
once at the global position and once for each subcommand.
The net effect is that the second registration shadows the first in
the resulting options object.

This may be something to address in pex (the global -v does nothing
so we should probably not register it), but the practical upshot
for Pants is that we have to provide the -v flag after the subcommand
name for it to take effect.

[ci skip-rust]

[ci skip-build-wheels]

The pex subcommands mechanism registers the -v flag twice,
once at the global position and once for each subcommand.
In practice the second registration shadows the first in
the resulting options object.

This may be something to address in pex (the global -v does nothing
so we should probably not register it), but the practical upshot
for Pants is that we have to provide the -v flag after the subcommand
name for it to take effect.

[ci skip-rust]

[ci skip-build-wheels]
@benjyw benjyw added the category:bugfix Bug fixes for released features label Apr 24, 2022
@benjyw benjyw requested review from Eric-Arellano and jsirois April 24, 2022 22:19
@benjyw
Copy link
Contributor Author

benjyw commented Apr 25, 2022

See corresponding pex issue: pex-tool/pex#1735

@benjyw benjyw deleted the pex_verbosity_arg branch April 25, 2022 21:18
@Eric-Arellano Eric-Arellano added this to the 2.11.x milestone Apr 25, 2022
Eric-Arellano pushed a commit to Eric-Arellano/pants that referenced this pull request Apr 25, 2022
The pex subcommands mechanism registers the -v flag twice,
once at the global position and once for each subcommand.
In practice the second registration shadows the first in
the resulting options object.

This may be something to address in pex (the global -v does nothing
so we should probably not register it), but the practical upshot
for Pants is that we have to provide the -v flag after the subcommand
name for it to take effect.

[ci skip-rust]

[ci skip-build-wheels]
Eric-Arellano pushed a commit to Eric-Arellano/pants that referenced this pull request Apr 25, 2022
The pex subcommands mechanism registers the -v flag twice,
once at the global position and once for each subcommand.
In practice the second registration shadows the first in
the resulting options object.

This may be something to address in pex (the global -v does nothing
so we should probably not register it), but the practical upshot
for Pants is that we have to provide the -v flag after the subcommand
name for it to take effect.

[ci skip-rust]

[ci skip-build-wheels]
Eric-Arellano added a commit that referenced this pull request Apr 26, 2022
…15249)

The pex subcommands mechanism registers the -v flag twice,
once at the global position and once for each subcommand.
In practice the second registration shadows the first in
the resulting options object.

This may be something to address in pex (the global -v does nothing
so we should probably not register it), but the practical upshot
for Pants is that we have to provide the -v flag after the subcommand
name for it to take effect.

[ci skip-rust]

[ci skip-build-wheels]

Co-authored-by: Benjy Weinberger <[email protected]>
@Eric-Arellano Eric-Arellano removed this from the 2.11.x milestone May 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:bugfix Bug fixes for released features
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants