oxidecomputer / oxidecomputer/buildomat
we should opportunistically compress responses
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Check run pages (e.g. https://buildomat.eng.oxide.computer/wg/0/details/01J04QGAYSFEA32EPBNB1NN9FA/rO6E1KLuz95lg5PhVtAw9IPDufYTSB5Uq4cxNubZy3ZUZVrG/01J04QHG82RKM5TEJTW822P8FP) can get quite large; this one is 3.56 MiB, but gzips to 275.51 KiB. Either Buildomat or Nginx could compress the response per the client's accept-encoding header.
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 inspecting the linked check-run page and how Buildomat or Nginx currently serves its response. Determine where client accept-encoding handling belongs, then verify that supported responses are compressed without changing their contents and that clients without compression support still work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx, rust
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100