Fix #819: Preserve microsecond precision when comparing date values in UniqueIterable - #819
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #819 +/- ##
=========================================
Coverage 96.35% 96.35%
Complexity 1152 1152
=========================================
Files 124 124
Lines 3540 3540
=========================================
Hits 3411 3411
Misses 129 129 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
vjik
approved these changes
Sep 16, 2026
samdark
changed the title
UniqueIterable
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.
UniqueIterabletreats distinct dates within the same second as duplicates becausegetTimestamp()discards microseconds. For example,14:05:01.000001and14:05:01.000002currently fail validation.