Skip to content

v0.12.36

Choose a tag to compare

@github-actions github-actions released this 30 Oct 13:00
· 11 commits to main since this release
2693010

v0.12.36 — a lost Docker connection is reported by its real cause

When logscry's connection to Docker's event stream broke and it retried, the status line sometimes named the wrong step: docker: events lost, reconnecting (attempt N, …): list: Cannot connect … instead of events: Cannot connect …. The Docker client library can report a refused connection a moment after it hands control back, so logscry's check occasionally ran first and went on to list the containers, and that request failed instead. Reconnecting always worked; only the reported cause varied, and the project's own test of it failed intermittently. Present since v0.12.34.

Found while working on #155.

What changed:

  • When a retry's container list fails, logscry now waits for the event subscription's own outcome and reports that, so a refused connection is always named as the subscription.
  • Successful reconnects, the number of requests made and the message for a Docker daemon that is unreachable at startup are unchanged.
  • Built with go1.26.10.

Measured:

  • The intermittent test, 500 runs under the race detector on a loaded 20-CPU machine: 58 failures before, 0 after.
  • With the race forced on every run: 100 of 100 failures before, 0 after.

Install: download the binary for your OS from the assets below, or go install github.com/maxie7/logscry/cmd/logscry@latest.

Known limitations:

  • No new ones from this change. The full list is in the README's Known limitations.

Tracked as #159.