Repository navigation
fix(configurator): retain runner observation freshness - #154
Merged
Merged
Conversation
lweberru
requested review from
Breeless,
JoshSTACKIT,
LembDo and
dweezl
as code owners
October 24, 2026 15:04
10 of 13 tasks
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.
Keep the actual time of the final stopped-Runner observation when completing an interrupted Application Plan. Previously a slow final S3 observation could move the timestamp forward and make an old Runner observation appear fresh.
Capture the timestamp immediately after checking the Runner and fail closed if the remaining State reads exceed 30 seconds; the existing database freshness check still protects the final transaction. Add deterministic regressions for a 29-second accepted observation and a 31-second rejected observation, including the exact timestamp passed to the database. No Runner/State/lock mutation or automatic execution is introduced.
Validation: 39 interrupted-Plan/CF-driver tests passed. Full application check passed (1,100 tests; 74 optional integration tests skipped). An initial sandbox-only run blocked local test HTTP listeners; the full check passed with those listeners permitted. No schema or UI changes. Dev deployment of PR #153 was cancelled before deployment so this correction can be included.
Refs #95.