fix(core): incorrect year rounding in case of leap years#6038
fix(core): incorrect year rounding in case of leap years#6038bluestreak01 merged 1 commit intomasterfrom
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing Touches🧪 Generate unit tests
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
1 similar comment
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing Touches🧪 Generate unit tests
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
[PR Coverage check]😍 pass : 2 / 2 (100.00%) file detail
|
|
@bluestreak01 @ideoma thanks for the reviews! |
Fixes #6029
YearTimestampSamplersampler had a bug around rounding. Namely, when the rounded year was a leap year and the input year wasn't, the returned result was incorrect.This bug manifested itself in materialized view refresh where the lo value of a range replace commit could end up being greater than the minimal timestamp of the transaction. The reason is that the range replace lo was calculated based on
YearTimestampSampler#round().