Avoid stack level too deep in predicate builder #41393
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
If you have an association with the same name as the foreign key then a
SystemStackError: stack level too deep
error is raised.This PR addresses the issue by checking if the
query
variable is different fromattributes
argument before recursively callingexpand_from_hash
. We have been running this fix in production for a number of years without issue at the company I work for.This issue has been mentioned in a number of issues #26778, #34869, #31110.
Other Information
Something to note is the setter for the association can raise errors. I have another branch that fixes that but I'm not sure if using an association extension is the best way to handle it.
Thanks