-
Notifications
You must be signed in to change notification settings - Fork 95
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
Maximum Recursion Depth Exceeded error when upgrading from 0.2 to 0.3 #60
Comments
Sadly no. And I also just noticed that I messed up adding those bloody tags for 0.3 so it would help a lot if you could a) test with the current version from github and b) post the stack trace (as useless as they seem, they do tend to at least show which recursion doesn't stop). From the top of my head the only place where recursion is used is during field generation. But that should stop. So no. Can't help you easily, but I'm happy to look into it :) |
Here's the stack trace - sorry for the delay! At the top I've listed all the libraries installed in my environment in case that is helpful as well.
|
Okay, as far as I can tell the document associated with your Could you copy & paste this document? It looks to me like the check that is used to guard from the infinite recursion is wrong and needs to be changed. But for that I would need to see what you do in your documents :) |
So, I took a closer look at it today and found an infinite recursion with two documents that reference each other like so: class ReferenceTestOne(Document):
ref_to_two = ReferenceField('ReferenceTestTwo')
class ReferenceTestTwo(Document):
ref_to_one = ReferenceField(ReferenceTestOne) Not sure if you do that in your application, but if you do it should hopefully work now with the above commit. |
I've been using MongoDbForms on a large project for quite a while and it's working great! Thanks! However, when I updated to the latest version (0.3), it's causing a maximum recursion depth exceeded error sitewide, with no real clarity in the stacktrace. Do you have any thoughts on why this might be occurring?
Thanks!
Lucas
The text was updated successfully, but these errors were encountered: