Repository navigation
A leading -- is still dropped for mvnd, oc, sbt, gt, bun, deno, docker compose, go test/build/vet and kubectl get #4919
Description
#4753 lists 19 commands whose leading -- clap strips before dispatch; #4768 restores it for those. The same loss happens on other passthrough arms the issue does not list.
argv a stub on PATH records for rtk <command> (develop 4b4bc40, and unchanged with #4768 merged):
| command | forwarded |
|---|---|
rtk mvnd -- zzz |
zzz |
rtk oc -- zzz |
zzz |
rtk sbt -- zzz |
zzz |
rtk gt -- zzz |
zzz |
rtk bun -- zzz |
zzz |
rtk deno -- zzz |
zzz |
rtk docker compose -- zzz |
compose zzz |
rtk go test -- zzz |
test -json zzz |
rtk go build -- zzz |
build zzz |
rtk go vet -- zzz |
vet zzz |
rtk kubectl get -- zzz |
get zzz |
The native command receives -- zzz in each case. mvnd shares mvn_cmd::run_tool with mvn, so after #4768 rtk mvn -- x and rtk mvnd -- x forward different argv.
Direction: the same dispatch-level restore as #4768 (restore_leading_double_dash in src/lib.rs), extended to these variants, with the restored -- placed after any option rtk injects (go test adds -json).
Activity
rtk-wshm-sync-bot commentedon Nov 1, 2026
🔍 Automated Triage
bugmediumSummary
Leading
--is dropped before dispatch for mvnd, oc, sbt, gt, bun, deno, docker compose, go test/build/vet, and kubectl get; extend restore_leading_double_dash in src/lib.rs to cover them.📁 Relevant files
src/lib.rsSuggested Actions
--is placed after rtk-injected options (e.g.-jsonforgo test)rtk mvn -- xandrtk mvnd -- xforward identical argvTriaged automatically by wshm · This is an automated analysis, not a human review.