Repository navigation
Fix agent directory refresh time after spring DST gap - #237
Merged
Merged
Conversation
Signed-off-by: Tiberiu Socaci <tsocaci@makeitfuture.com>
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
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.
When the local 03:00 refresh falls in a spring daylight-saving gap, JavaScript normalizes it to 04:00. Advancing that normalized Date kept the following day at 04:00. Reset the intended hour after advancing the calendar date so ordinary days return to 03:00.
The regression runs in Europe/Bucharest and covers the missing hour, next-day rearm, ordinary dates and the autumn repeated hour. It fails before the fix and passes after it. All 30 focused directory tests pass; fresh full-rule disposable lifecycle, MCP and scheduled/background delivery acceptance passes 33 tests with zero skips. Provider clients are explicitly simulated; there are no live external posts.
Updated FEATURES.md, TEST-PLAN.md and CHANGELOG.md. Independent review approved the exact signed commit. Full coverage passes 4,451 tests (zero failures; ten opt-ins separately exercised by 14 actual container checks with zero skips and no resource delta). Static checks, history secret scan, security coverage, production dependency audit, DCO and release artifacts all pass. GitHub CI remains a prerequisite for coordinator-controlled landing.