sillsdev / sillsdev/languageforge-lexbox
504 Gateway Timeout on large pushes with slow Internet
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 9
- Forks
- 8
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 49
Description
While trying to solve #310, I did a kubectl port-forward to bypass the ingress controller and connect directly to the Lexbox API container. That worked, and I did not get a 413 Request Entity Too Large error... but I did get a 504 Gateway Timeout. The HTTP POST took over 15 minutes to complete, which is probably the cause of the 504. But we need to test this scenario: once we've solved the 413 errors, we should test a large hg push with an Internet connection deliberately degraded to about 1 MiB/s so that a one-gigabyte POST takes over 15 minutes.
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 reviewing issue #310 and the existing ingress-controller path, then compare it with the successful kubectl port-forward to the Lexbox API container. After the 413 case is resolved, reproduce a one-gigabyte hg push over a deliberately degraded connection near 1 MiB/s and verify whether the request still returns a 504 after more than 15 minutes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- api, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100