FlexMeasures / flexmeasures / 40716641511

87%

push

github

Keep days calendar days across DST in offset chains (DB, HB, nD) (#2771)

* Apply offset chains on the local wall clock, so days stay calendar days across DST

Before Pandas 3, a "1D" offset is a fixed 24 hours, so "2D,DB" from just after midnight on the day before clocks go back resolved to the next day instead of the day after,
e.g. emptying an automation's window.
"HB" raised in the repeated hour, and "DB" raised where a day begins in a DST gap (America/Santiago).
Day offsets and day/hour begins now act on the local wall-clock time:
a time that occurs twice keeps its DST side, and a time that does not exist shifts forward.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: F.N. Claessen <claessen@seita.nl>

* docs: changelog entry for PR #2771

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: F.N. Claessen <claessen@seita.nl>

* Fall back to exactly 24 hours per day where a wall-clock time is ambiguous or does not exist

This makes the policy symmetric across both DST transitions:
02:30 + 1D lands 24 hours later on both the fold and the gap (02:30 CEST and 03:30 CEST, respectively),
rather than keeping the DST side on the fold but shifting to the end of the gap.
Day and hour begins keep their own handling.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: F.N. Claessen <claessen@seita.nl>

---------

Signed-off-by: F.N. Claessen <claessen@seita.nl>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

17 of 18 new or added lines in 1 file covered. (94.44%)

22805 of 26171 relevant lines covered (87.14%)

0.87 hits per line