Fix incorrect keying of by= results involving functions of keys #6708
Conversation
This file contains 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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #6708 +/- ##
=======================================
Coverage 98.61% 98.61%
=======================================
Files 79 79
Lines 14553 14564 +11
=======================================
+ Hits 14352 14363 +11
Misses 201 201 ☔ View full report in Codecov by Sentry. |
|
Generated via commit 5c98a77 Download link for the artifact containing the test results: ↓ atime-results.zip
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #5583.
In principal this could be a breaking change for some user that has
by = .(a = foo(a))whereais the key andfoo()is weakly increasing.If we find any such case in revdeps, I will bump this change to 1.18.0 (there is a known workaround for the bug, i.e. use
keyby=, and the bug appears to have taken quite some time to surface) and push the breaking change in next release. As a breaking change, the fix is also trivial (switch tokeyby=).