Add ScopesUtil.printScopesChain for debugging
#4443
Merged
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.
#skip-changelog
📜 Description
Add
ScopesUtil.printScopesChainfor debugging what the chain ofScopeslooks like by traversing theparentand printingScopesandScopeobject IDs as well ascreatorstring.Looks like this:
💡 Motivation and Context
Helps us investigate things like scope forking (or lack thereof) and scope bleeding.
We can use this to ask customers to attach this to GH issues for quicker support and also for making sure we're reproducing what's actually happening.
💚 How did you test it?
📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps