Initial turn requests do not use network retry logic
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 16
- Forks
- 3
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 121
Description
JP version
jp v0.1.0-43d34410 (2026-08-08)
What happened?
network error: error sending request for url ...
On (yet another) admittedly bad network, jp q chat_requests often immediately drop into network errors. Once the initial request is sent, the retry logic kicks in.
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 at the jp q chat request path and compare how the initial request is sent with the retry logic used after the first request. Done means initial-turn network failures follow the same retry behavior instead of immediately returning an error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100