rtk-ai/rtk

cargo output on success is too terse, making it ambiguous

Open

#759 建立於 2026年3月21日

在 GitHub 查看
 (2 留言) (0 反應) (0 負責人)Rust (48,085 star) (2,914 fork)batch import
bugeffort-smallfilter-qualitygood first issue

描述

cargo check returned cargo build (0 crates compiled)

which - to claude - was ambiguous - it didn't know if there were errors or not, so it tried several work-arounds, consuming extra tokens.

as work-arounds, it ran rtk proxy cargo check, and RUSTFLAGS="-D warnings" rtk proxy cargo check

Claude said it expected to see the "Finished dev profile ..." message.

Suggestion: include the 'Finished ...' message in the success output

貢獻者指南

技術棧
rust
領域
clideveloper experience
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
under 1 hour
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic Rust knowledge
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
90
研究方向
Examine the command execution module in the codebase, likely in a file like `src/commands.rs` or `src/proxy.rs`. Find where `cargo check` output is captured and printed. Add logic to include the 'Finished' message from cargo's stderr/stdout when the command succeeds. Ensure the change is minimal and does not affect error handling. Consider adding tests for the output format.
cargo output on success is too terse, making it ambiguous · rtk-ai/rtk#759 | Good First Issue