This repository was archived by the owner on Sep 17, 2026. It is now read-only.
Reconcile orphan queue intents and make member maintenance preserve workers - #457
Merged
Merged
Conversation
Signed-off-by: rldyourmnd <danil@nddev.it.com>
…ntenance Signed-off-by: rldyourmnd <danil@nddev.it.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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Periodic queue reconciliation previously depended on a workflow-job DB row that normal webhook cleanup could already have removed. Authoritative rehydration also omitted the workflow run ID. The new GARM .95 retains that identity and independently selects old journal candidates, then verifies the exact GitHub GUID/repository/run/attempt/check URL/source/scale-set identity before writing a terminal receipt. Unknown, running, foreign, incomplete and ambiguous work is preserved; legacy discovery and retries are bounded.
Member maintenance no longer force-stops containers by a warm-name prefix: a claimed warm retains its name. Full drains wait for every occupant and warm retirement stays with the provider's claim-aware path. The new --fence-only mode closes placement while reporting, and preserving, existing work.
GARM .95 uses reviewed current vendored Go dependencies and Go 1.27.1. Provider .133 binds the independent network-dependency commit. Both artifacts were reproduced twice with identical bytes; GARM retains the GLIBC 2.34 ABI ceiling. Source vulnerability verification reports zero affected imported packages/reachable symbols; the sole module-only openpgp advisory refers to packages absent from the production closure, with no suppression added.
Validation: full public make verify; full GARM vet and race suites in a network-disabled pinned build image; real SQLite/native-journal regressions for missing DB rows, running-sibling preservation, terminal receipts/restart, identity/refusal/ambiguity and retry budgets; drain/fence CLI and race tests; native repository projection apply/verify/check from verified GDS0.9.4. Candidate wrapper's final positional version probe failed after successful tests/builds; the correct --version probe passed and the original wrapper result is retained. Canonical hosted derivative reproduction remains the independent publication check. No consumer runtime, application configuration or GitHub jobs are changed by this public source PR.