Changed closure and change detection logs are giving the same information and confusing
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5
- Forks
- 1
- Avg merge
- 17h 48m
- Merged PRs (30d)
- 2
Description
2025-10-14T16:59:53.545210Z INFO cargo_fslabscli::commands::check_workspace: Changed packages: [
"package_a
]
2025-10-14T16:59:53.545399Z INFO cargo_fslabscli::commands::check_workspace: Changed closure: [
"package_a",
"subpackage_b/package_b",
]
2025-10-14T16:59:53.545466Z INFO cargo_fslabscli::commands::check_workspace: Detected change in "package_a"
2025-10-14T16:59:53.545481Z INFO cargo_fslabscli::commands::check_workspace: A dependency changed for "subpackage_b/package_b"
We should keep one or the other
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start in the cargo_fslabscli::commands::check_workspace entry point, which produces the duplicated change logs shown in the issue. Compare the changed-packages, changed-closure, and per-package messages, then retain the single form that communicates the needed information and verify the resulting check output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100