WordPress / WordPress/contributor-toolkit
Uploading a large file to a pull request can die on the request timeout
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 36
- Forks
- 13
- Avg merge
- 23h 19m
- Merged PRs (30d)
- 72
Description
What
Every GitHub request shares one 15-second timeout. That was sized for small JSON reads; opening a pull request (#167) now sends file contents through the same path, and a large binary on slow venue wifi can exceed it.
Why it matters
The failure reads as "no connection to GitHub" — wrong twice over: the network is fine, just slow, and by then earlier files have already uploaded. Contributor Day wifi is the normal environment, not the edge case.
Idea
A longer ceiling for uploads than for reads, sized to content length rather than one constant for everything.
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
Trace the GitHub request path used when opening a pull request and uploading file contents, then locate the shared 15-second timeout. Check how content length is available during uploads and how earlier files are handled after a timeout. Done means uploads have a longer content-aware ceiling while ordinary reads retain their existing timeout and slow-network failures are reported accurately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- api, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100