Skip to content

Conversation

bvinc
Copy link
Contributor

@bvinc bvinc commented Aug 4, 2025

Running buck2 debug chrome-trace in debug mode would panic as clap has a debug assert to check for duplicate argument IDs. It is my understanding that duplicating argument IDs can cause bugs in release mode, even if they are under different subcommands.

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Aug 4, 2025
@facebook-github-bot
Copy link
Contributor

@facebook-github-bot has imported this pull request. If you are a Meta employee, you can view this in D79596226. (Because this pull request was imported automatically, there will not be any future comments.)

@lf-
Copy link
Contributor

lf- commented Aug 5, 2025

this fixes #1029, please add a note in the commit message :)

Running `buck2 debug chrome-trace` in debug mode would panic as clap has a debug
assert to check for duplicate argument IDs.  It is my understanding that
duplicating argument IDs can cause bugs in release mode, even if they are under
different subcommands.

This also fixes the same panic that can occur during "buck2 completion zsh",
issue facebook#1029.
@bvinc bvinc force-pushed the chrome_trace_event_log_arg branch from 07eea5d to 958597a Compare August 6, 2025 17:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants