sneak/pixa - pixa - git.eeqj.de

211 Commits 11 Branches 0 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
clawbot	92e48a7a91	Test the warnings a stop logs and stopping between eviction candidates The stop-during-reconciliation test now also expects exactly one warning; it fails while the loop still starts an eviction pass after a cancelled reconciliation. A new test cancels the context while the oldest of three source blobs is evicted and expects EvictToLimit to return context.Canceled, leave the other two on disk and log no warning for them. Model: opus-5-5	2026-10-04 06:45:53 +00:00
clawbot	d930e352b0	Stop cache eviction in progress at shutdown (closes #102 ) StartEviction runs the eviction goroutine with its own context, which StopEviction cancels in place of the old stop channel, so a pass in progress stops at its next database call, file, row or eviction candidate instead of running to completion. StopEviction takes a context: when it ends before the goroutine exits, StopEviction stops waiting and returns an error wrapping it. The handlers' stop hook passes fx's stop context, so an eviction still running at fx's stop deadline fails the stop and the exit code is 1. The contextcheck suppression on the start hook stays, with a one-line reason: the loop outlives OnStart. Model: opus-5-5	2026-10-04 06:45:53 +00:00
clawbot	04b5db6fbf	next -> main (1.0.0 milestone) (#105 ) check / check (push) Successful in 5s Details Accumulating milestone branch. One squashed commit per closed issue; `next` is kept green and mergeable to `main` at any time without notice. Landed so far: - `chore: update golangci-lint to v2.12.2 with canonical config` (#54) — canonical v2-schema `.golangci.yml`, pins bumped in `Dockerfile` and `script/bootstrap`, tree at `0 issues.`. Three behaviour deltas are recorded in that PR's body: `Cache.StoreVariant` takes a context, `MetadataStorage.Store` no longer leaks temp files on failure, and the `signing_key` too-short error text gained a `value too short:` prefix. Sequencing for the milestone is tracked in #103. Reviewed-on: #105 Co-authored-by: clawbot <clawbot@noreply.example.org>	2026-09-21 09:31:54 +02:00

Author

SHA1

Message

Date

clawbot

92e48a7a91

Test the warnings a stop logs and stopping between eviction candidates

The stop-during-reconciliation test now also expects exactly one
warning; it fails while the loop still starts an eviction pass after a
cancelled reconciliation. A new test cancels the context while the
oldest of three source blobs is evicted and expects EvictToLimit to
return context.Canceled, leave the other two on disk and log no
warning for them.

Model: opus-5-5

2026-10-04 06:45:53 +00:00

clawbot

d930e352b0

Stop cache eviction in progress at shutdown (closes #102 )

StartEviction runs the eviction goroutine with its own context, which
StopEviction cancels in place of the old stop channel, so a pass in
progress stops at its next database call, file, row or eviction
candidate instead of running to completion. StopEviction takes a
context: when it ends before the goroutine exits, StopEviction stops
waiting and returns an error wrapping it. The handlers' stop hook
passes fx's stop context, so an eviction still running at fx's stop
deadline fails the stop and the exit code is 1. The contextcheck
suppression on the start hook stays, with a one-line reason: the loop
outlives OnStart.

Model: opus-5-5

2026-10-04 06:45:53 +00:00

clawbot

04b5db6fbf

next -> main (1.0.0 milestone) (#105 )

check / check (push) Successful in 5s

Details

Accumulating milestone branch. One squashed commit per closed issue; `next` is kept green and mergeable to `main` at any time without notice.

Landed so far:

- `chore: update golangci-lint to v2.12.2 with canonical config` (#54) — canonical v2-schema `.golangci.yml`, pins bumped in `Dockerfile` and `script/bootstrap`, tree at `0 issues.`. Three behaviour deltas are recorded in that PR's body: `Cache.StoreVariant` takes a context, `MetadataStorage.Store` no longer leaks temp files on failure, and the `signing_key` too-short error text gained a `value too short:` prefix.

Sequencing for the milestone is tracked in #103.

Reviewed-on: #105
Co-authored-by: clawbot <clawbot@noreply.example.org>

2026-09-21 09:31:54 +02:00