oxidecomputer / oxidecomputer/progenitor
Fails to parse Alertmanager API
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1k
- Forks
- 136
- Avg merge
- 8h 36m
- Merged PRs (30d)
- 14
Description
https://github.com/prometheus/alertmanager/blob/main/api/v2/openapi.yaml
Error:
paths: data did not match any variant of untagged enum ReferenceOr at line 21 column 3
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 opening Alertmanager’s api/v2/openapi.yaml, especially around line 21, and trace the parser path that reports the ReferenceOr error. Compare the document’s paths structure with the parser’s accepted variants; done means the specification parses successfully without that error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi, rust
- Domain
- api, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100