Missing transition checker#4884
Open
faithokamoto wants to merge 4 commits intomasterfrom
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Changelog Entry
To be copied to the draft changelog by merger:
Description
If you uncomment
//#define debug_missing_transitionand then run a zipcode tree chaining problem, thefind_missing_zip_tree_transitions()function will do a very crude but comprehensive check of all possible seed-to-seed transitions, in all possible orientations, and see if those transitions were missed bygenerate_zip_tree_transitions(). Any missing ones will lead to the offending transitions being printed out and an error.Just a generally useful debugging tool of last resort when you can't figure out why a ziptree is misbehaving.