Skip to content
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 #37

Open
oldani opened this issue Nov 14, 2019 · 3 comments
Open

*** RecursionError: maximum recursion depth exceeded #37

oldani opened this issue Nov 14, 2019 · 3 comments
Labels

Comments

@oldani
Copy link

oldani commented Nov 14, 2019

When I call gql_optimizer.query(myquery, info) it always raises RecursionError not matter witch query I pass in.

Python 3.7
Django 2.2.7
Graphene-Django 2.6.0

I tried with 0.6.0 and 0.6.1

@NyanKiyoshi
Copy link
Collaborator

Hi!

Could you provide us the models, the query, info context and error stack? Feel free to make a zip of the files or something as it would make the life easier to reproduce.

Thank you!

@tpict
Copy link

tpict commented Mar 13, 2020

I had this issue when passing through a queryset whose model queried DB fields in its __init__ method–the fix was just to move that code elsewhere. I wonder if it's something that could be guarded against.

@untidy-hair
Copy link

untidy-hair commented Feb 8, 2022

I just encountered this issue. Similar to what @tpict said, there was a model.signals.post_init setup which uses the DB model field values. I don't want to change the setup of the model if possible so I'm wondering if there's a way to guard it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants