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.
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
Improve
AssertionError
error message for sequences inside dictionaries #12717base: main
Are you sure you want to change the base?
Improve
AssertionError
error message for sequences inside dictionaries #12717Changes from 5 commits
e60e7ee
1d3d99e
5210674
6c5a720
770d8ba
a1b0239
41c48fb
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure I like this approach, given this is really only specific for sequences inside dictionaries... this is not general because really we could have anything in there, for example other dicts or dataclasses, each with their own custom diff code... 🤔
The core of the original issue was the fact that it was truncating the diff. One idea is to not truncate anything when computing the diff, however truncation is there for a reason, to avoid dumping MBs of text in case of large data structures...
I'm a bit -1 on this solution, given it only fixes a very specific use case and makes the code slightly worse, but I don't have a definitive suggestion either.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I initially thought we could take all the cases in
_compare_eq_any
and use those to create the new diffs but they seemed too long for cases outside of sequences due to their multi-line diffs, e.g.:Besides this though, I figured sequence comparisons would be the most likely use case, and it'd be worth having it there despite the bit of complexity. I could be wrong though!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An alternative method might be to figure out a truncated diff for the other data types such as a simple
Differing items
for each instead of their specific diffs, but this seems overkill for just comparisons within dictionaries