You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 9c228ad
Browse filesBrowse the repository at this point in the historyBrowse files
Sweep leftover path identity probes in startup recovery (#181) (#192)
* Sweep leftover path identity probes in startup recovery (#181)
The probe's container and anonymous volume now carry the database's runner
token and `io.codeboost.probe=path-identity`, a label shape for runner-scoped
objects. Startup recovery, under the runner lock, removes this runner's probe
containers (by full ID) and then their volumes (by name), and leaves anything
of another runner, anything without the probe kind, and anything with attempt,
allocation or other kind labels. A probe without a runner label is reported.
Closes#181
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Answer volume removal as Docker 27.4 does; exact probe label wording (#181)
Review round 1: the fake daemon exits 0 for a missing volume under --force
and refuses a volume a container mounts; tests for a refused probe container
and a malformed runner token; docs state the probe exception to the scoped
recovery rule and what an orphaned client can do.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Keep a probe volume still in use; recheck the runner label by name (#181)
Review round 2: a probe volume that a container recovery leaves still mounts
is kept for a later start rather than failing every start; a probe volume
counts only with this runner's label, since it is removed by name; a lone
leftover volume is tested; doc wording.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Skip objects relabelled before the inspect; fake rm --force as Docker 27.4 (#181)
Review round 3: an object listed under this runner but inspected with
another's is neither removed nor reported; the fake's rm --force of a missing
container exits 0, as Docker 27.4 does; the kept in-use volume's wording says
it goes once its holder is gone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Say exactly when an orphaned probe is kept or missed; keep --rm in the fixture (#181)
Review round 4.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
thrownewError(`${failure.message} The probe container ${name} may remain; remove it with docker rm --force --volumes ${name}.`,
461
+
thrownewError(`${failure.message} The probe container ${name} may remain; the next start's recovery removes it, or remove it now with docker rm --force --volumes ${name}.`,
0 commit comments