Skip to content

Conflicting short argument -p #3205

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

Open
1 of 4 tasks
leejuyuu opened this issue May 1, 2025 · 0 comments
Open
1 of 4 tasks

Conflicting short argument -p #3205

leejuyuu opened this issue May 1, 2025 · 0 comments

Comments

@leejuyuu
Copy link

leejuyuu commented May 1, 2025

System Info

Arch Linux
NVIDIA-SMI 550.90.07 Driver Version: 550.90.07 CUDA Version: 12.4

Information

  • Docker
  • The CLI directly

Tasks

  • An officially supported command
  • My own modifications

Reproduction

When running the trtllm backend on 39cfe23 with the dev profile, I found the following panic.

thread 'main' panicked at /home/linuxuser/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/clap_builder-4.5.32/src/builder/debug_asserts.rs:112:17:
Command text-generation-backends-trtllm: Short option names must be unique for each argument, but '-p' is in use by both 'port' and 'prometheus_port'

I tested that removing the short from line 40 here resolves this problem.

#[clap(default_value = "3000", long, short, env)]
port: u16,
#[clap(default_value = "9000", long, short, env)]
prometheus_port: u16,

Reproduction step:

 cargo build --profile dev --package text-generation-backends-trtllm --bin text-generation-backends-trtllm
./target/debug/text-generation-backends-trtllm

Expected behavior

The panic should not happen and should output this.

error: the following required arguments were not provided:
  --tokenizer-name <TOKENIZER_NAME>
  --model-id <MODEL_ID>
  --executor-worker <EXECUTOR_WORKER>

Usage: text-generation-backends-trtllm --tokenizer-name <TOKENIZER_NAME> --model-id <MODEL_ID> --executor-worker <EXECUTOR_WORKER>

For more information, try '--help'.
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

No branches or pull requests

1 participant