chomp errors not easily showing the cause
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 168
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
When running a large number of tasks, an error on a specific task can be hard to trace to the exact task which caused the error.
We should more carefully manage the output when an error happens to ensure there is a proper report summary at the end as to which task failed.
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 by reproducing a large task run with one failing task and trace how Chomp reports errors and finishes its output. Done means the final report identifies the failed task and retains enough of the original error to show its cause.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100