bookworm build cannot be cancelled
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16
- Forks
- 3
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 121
Description
When I attempt to cancel during bookworm's build, I expect immediate feedback.
In the self-dev repository for JP, if /target/ is refreshed, per #845, bookworm administration causes a silent build process and query failure.
The scope of this issue is not that it is too slow, but that it is blocking.
jp q --new --cfg dev -- "test"
^C^C^C^C^C
MCP error
Timeout error: deadline has elapsed
deadline has elapsed
As in #845, what actually happened is that bookworm took its time, but completed successfully, so retrying the query will succeed.
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 the cancellation behavior in the self-dev repository with jp q --new --cfg dev -- "test" while bookworm builds, including repeated Ctrl-C. Compare the behavior described in #845 and trace the bookworm build and query path. Done means cancelling provides immediate feedback instead of a silent process and timeout, without preventing successful retries after a completed build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100