instrumenta / instrumenta/openapi2jsonschema
Parsing large OpenAPI documents leads to memory issues
Open
- Dominant language
- Python
- Stars
- 248
- Forks
- 95
- PR merge metrics
- No merged PRs in 30d
Description
E.g. if you parse the Kubernetes swagger.json (~5.1MB of JSON as of this issue), even with a pretty beefy machine, you eventually run out of memory.
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the memory issue by parsing the Kubernetes swagger.json mentioned in the report, then inspect the parser entry point and its handling of large OpenAPI documents. Done means the document parses without exhausting available memory and the existing behavior for generated schemas remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi, python
- Domain
- api, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100