-
-
Notifications
You must be signed in to change notification settings - Fork 56
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
Panic During Schema Rendering #285
Comments
Hi, What will really help me diagnose this problem is a blob of code I can copy and paste into my test-rig and debug the issue, the problem with snippets like this is that I have no idea how your source is structured or your base specification etc. I really don't have the luxury of time to re-create this issue by reverse engineering the code you've provided. I really need something that will re-create the issue, that runs as a test or that will run as a copy paste job. Thanks. |
Hi @daveshanley! Here is the gist with all the information to reproduce the error: https://gist.github.com/matteogastaldello/823cdaf0127c2f2eaa92ddb574539825 Thanks a lot! |
nill checks added to prevent explosions.
nill checks added to prevent explosions.
Resolved in |
Hi!
I'm encountering a runtime panic due to an invalid memory address or nil pointer dereference when attempting to render a schema using the libopenapi library. This issue arises during the execution of the schema.Render() method, which results in a segmentation violation error.
These are the lines that throws the panic
This error occurs if schema.Required is not previously set in the oas specification used to build the model. Setting a "fake" required field in the oas specification file fix the behaviour.
Thanks for your help
The text was updated successfully, but these errors were encountered: