fix: two more 'services stop' hints print a command without --yes
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Under an hour
- Newbie friendliness
- 78/100
Research direction
Start at the two printed hints: the rocm services stop {} message near apps/rocm/src/main.rs:7210 and the {remote_cli} services stop {service_id} message near apps/rocm/src/remote/mod.rs:732. Compare them with the approval gate in run_approved_service_action and the canonical form asserted in service_actions_require_yes_and_render_sandbox_result. Done when both hints include --yes and the existing tests at main.rs:30676 and remote/mod.rs:1545 are tightened to check the full command.
Written by the indexing model from the issue text.
Description
Bug
Two more places print a rocm services stop <id> hint without --yes, the same drift #417 and #601 fixed in the serve summary's stop row. run_approved_service_action refuses any stop/restart that omits --yes, so both of these teach a command the CLI then rejects:
apps/rocm/src/main.rs:7210— the "already running without auth" bail message tells the user to stop it withrocm services stop {}(no--yes).apps/rocm/src/remote/mod.rs:732— the "reused service" bail message tells the user to run{remote_cli} services stop {service_id}(no--yes).
Both are real, user-facing instances of the same bug class identified during review of #601. Their existing tests (main.rs:30676, remote/mod.rs:1545) only check a substring of the message, so neither would catch this.
Suggested fix
Same minimal fix as #601: add --yes to both printed hints, matching the canonical form service_actions_require_yes_and_render_sandbox_result already asserts the approval gate recommends.
#601 also raised a related non-blocking suggestion: the stop/restart hint is currently formatted by hand in at least eight call sites across main.rs and remote/mod.rs. A shared stop_hint(service_id) / restart_hint(service_id) helper, in the spirit of run_approved_service_action's own advice already being derived from the same value the branch is taken on, would prevent this class of drift going forward rather than only fixing today's two instances.
References
- #417 (original serve-summary drift)
- #601 (serve-summary fix; surfaced these two during review)
- Dominant language
- Rust
- Stars
- 41
- Forks
- 10
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 87
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ROCm/rocm-cli
-
Move the remaining `scripts/` tooling to Rust (`cargo xtask` / e2e scenarios)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
serve: the post-launch smoke test spins forever at 100% CPU if the engine closes the connection mid-responsePossibly taken @rominf claimed this 5 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ROCm/rocm-cli#514 · 1 comment ·
Maintainers usually reply within 1 day
-
examine: lspci cannot name a GPU that pci.ids does not know, though the device id is on the lineOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
chroma-core/chroma#7879 ·
Maintainers usually reply within 1 day
-
priority middle
Difficulty 1/5 Under an hour Newbie friendliness 72/100
KATO-Hiro/AtCoderClans#12838 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day