oxidecomputer / oxidecomputer/buildomat
Errors parsing incoming GitHub webhooks
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
I was looking at the production buildomat logs, and these lines appeared a lot:
delivery XXX event check_run: unknown variant `waiting`, expected one of `queued`, `in_progress`, `completed`, `pending`
delivery XXX event check_run: unknown variant `waiting`, expected one of `queued`, `in_progress`, `completed`, `pending`
delivery XXX event check_run: unknown variant `waiting`, expected one of `queued`, `in_progress`, `completed`, `pending`
delivery XXX event pull_request: invalid type: null, expected a string
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 files, tests, or entry points are named. Trace the incoming GitHub webhook parsing for check_run and pull_request events, then reproduce the reported payload variants; done means these valid events are accepted without the logged parsing errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, rust
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100