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

Prevent possible recursion limit issue in migration planning #3169

Closed
wants to merge 1 commit into from

Conversation

bwreilly
Copy link

@bwreilly bwreilly commented Sep 5, 2014

This switches out the recursive depth first search for stack based approach.

Additionally adds test that replicates original potential problem.

@collinanderson
Copy link
Contributor

If possible, please separate out the whitespace changes from the actual code changes. Also, patches should generally be against the master branch (instead of 1.7.x)

@bwreilly
Copy link
Author

bwreilly commented Sep 5, 2014

Going to do this against master, and remove whitespace changes.

@bwreilly bwreilly closed this Sep 5, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants