kworkflow / kworkflow/patch-hub
patch-hub error-exits after going to the next page
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 36
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Description:
Going into the Git's mailing list, the first page loads correctly, however after going to the next page (older), patch-hub error-exits.
How to reproduce:
Going into Git's mailing list today and go to the next page (older).
Expected behavior:
To be able to move through pages.
Screenshots
Error:
0: Http(
Net(
Other(
"the response body is larger than request limit: 10485760",
),
),
)
Location:
src/app/screens/latest.rs:60
Setup:
- Project branch: unstable
- Project commit hash: 750c40b
Contributor guide
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 src/app/screens/latest.rs:60 and reproduce the error by opening Git's mailing list and selecting the next older page. Trace how that page's response is handled when it exceeds the 10485760-byte request limit. Done means navigating to older pages no longer causes patch-hub to error-exit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100