oxidecomputer / oxidecomputer/progenitor
gen fail: TypeError(InvalidValue) on openAI scheme
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1k
- Forks
- 136
- Avg merge
- 8h 36m
- Merged PRs (30d)
- 14
Description
Here's the scheme source https://github.com/openai/openai-openapi/blob/master/openapi.yaml
Here's the call:
RUST_BACKTRACE=1 cargo progenitor -i openapi.yaml -o openai -n openai -v 2.0.0
Here's the stack:
gen fail: TypeError(InvalidValue)
Error: generation experienced errors
Stack backtrace:
0: std::backtrace::Backtrace::create
1: anyhow::error::<impl anyhow::Error>::msg
2: cargo_progenitor::main
3: std::sys::backtrace::__rust_begin_short_backtrace
4: std::rt::lang_start::{{closure}}
5: std::rt::lang_start_internal
6: _main
If to be used by macro generate_api!("/.../openai-openapi/openapi.json"); the error if different:
error proc macro panicked rustc
message: Failed to make unique variant names for [Array,Array,Array]
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 reproducing the failure with RUST_BACKTRACE=1 cargo progenitor -i openapi.yaml -o openai -n openai -v 2.0.0 using the linked OpenAI openapi.yaml. Compare it with the generate_api! invocation and its “Failed to make unique variant names” error. Done means the OpenAI schema no longer causes either generation path to fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi, rust
- Domain
- api, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100