-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0xb337d2
#128
Comments
This has been fixed in However, it won't operate as expected, because you cannot compare a v2 spec and a v3 spec. |
Thank you! That's perfect. |
Ah @daveshanley would it be possible to write |
Using arch linux I downloaded
https://github.com/pb33f/openapi-changes/releases/download/v0.0.61/openapi-changes_0.0.61_linux_x86_64.tar.gz
Then I executed
./openapi-changes report api-with-examples_2.0.yaml api-with-examples_3.0.yaml
(The files are https://raw.githubusercontent.com/OAI/OpenAPI-Specification/main/examples/v2.0/yaml/api-with-examples.yaml and https://raw.githubusercontent.com/OAI/OpenAPI-Specification/main/examples/v3.0/api-with-examples.yaml)
Which resulted in
Using the console output it just results in an endless "generating model for commit bla".
This is a
v2
vsv3
report.If I try a
v3
vs a completely differentv3.1
report it works.The text was updated successfully, but these errors were encountered: