Repository navigation
fix: preserve selected updates across slow Docker stops - #25
Merged
Merged
Conversation
Keep shutdown grace unchanged while bounding stop acknowledgement time, retain safe primary and recovery diagnostics, and recognize the exact pinned released proxy configuration without changing existing Fleet guard behavior.
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.
Selected updates can roll back when Docker acknowledges a stopped container just after the client deadline. Give only the stop response additional bounded time, keep the existing shutdown grace, and retain safe primary/recovery failure details.
Support guarded upgrades from the released 1.5.4 configuration through an isolated, pinned historical template closure. Existing Fleet recovery, identity, selection and configuration checks are preserved.
Validation: