-
-
Notifications
You must be signed in to change notification settings - Fork 772
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
Swagger UI Infinite Recursion Issue in 3.2.0 #2028
Comments
Same here, initially we thought there was an update with the openapi schema but didn't find anything suggesting that. We did find however that there was a change around jsonschema: #1974. Fixed our version to 3.1 until this is resolved |
Looked a bit closer and found that one of my recursive schemas is the source of the infinite recursion during the json validation. Here's an idea of what the schema looks like:
When I get a chance I'll try to figure out which part of the diff between v3.1 and 3.2 caused this problem to surface |
Alright I narrowed it down to it being just this change that caused this issue: merged from this PR: #2002 When I revert that self._spec to self._raw_spec, the validations around my self-referencing json schema pass and no longer run into a stackoverflow. I gave it a decent try to understand what's going wrong internally in connexion, but I couldn't figure it out unfortunately. I'll just be monkey-patching connexion to revert this particular change so that we can use 3.2.0. I think @RobbeSneyders should know about the regression that change has caused though |
We recently upgraded to the latest version of Connexion due to the
python_multipart
package issue.to
Everything seemed to be working fine, but we can't access our Swagger UI page anymore. If we attempt to, we get a 500, and the logs show this:
Any ideas for the cause of the regression?
The text was updated successfully, but these errors were encountered: