-
Notifications
You must be signed in to change notification settings - Fork 35
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
RecursionError: maximum recursion depth exceeded while calling a Python object #251
Comments
Hey, which version of |
I updated the library I was using to 0.11 to be sure and it manifested the same behavior. Unfortunately, this is an internal API I can't share details of publicly, but I am going to do some digging and review the schema and see what could be self-referential and revert back with thoughts. |
Hello! I am facing exactly the same issue with TypeGraphQL+Prisma generated API. |
I have made a small investigation, and it seems that starting from a certain level of complexity of the schema this error just happens. Though, this time I was able to get a little bit better error message: Most probably it could be resolved by setting higher recursion limit somewhere in the code, like: Here is a little reproduction I was able to make: |
Thank you for this reproduction. I'll give it a look but just the "too big schema causes problems" observation seems to point that we need to change recursive algorithm to linear one 🤔 |
Interesting... Poked this again today, and messed with the recursion limit setting -- still seeing a recursion error which indicates to me I might have a circular relationship in my DB schema, which theoretically should be fine because I set the field resolution depth to 3 on my backend, but I suspect it messes with the way you're rendering the pydantic types. I suspect a switch to a linear algorithm might address both issues. |
Hey there!
I am testing out ariadne-codegen against a TypeGraphQL-generated API and am seeing issues at runtime that look pretty similar to #100.
I have a node SDK which uses GraphQL Codegen that handles this API just fine so thinking there's a bug in this library somewhere that is interacting weirdly with my schema.
The text was updated successfully, but these errors were encountered: