opensafely-core / opensafely-core/proxy
503s from github until restart
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 1
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 1
Description
We started getting 503s from github at around 5am this morning, from our fresh ping.
Restarting the dokku app fixed the issue.
It wasn't all urls (e.g. /info/refs seemed to work), but we couldn't checkout via the proxy until we restarted.
Possibly the connection got in a stuck state. We could maybe try using http/1.0 rather than http/1.1 if this happens again.
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
No file, test, or entry point is named. Start by examining how the proxy handles GitHub connections and reproduce the intermittent 503 behavior around checkout requests; done means identifying and preventing the stuck connection condition without breaking working endpoints such as /info/refs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, shell
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100