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
claim_next in scripts/zarr/zarr_queue.py does a SELECT followed by an UPDATE without an explicit transaction, while its docstring says "Atomic under the connection's write lock". Two concurrent callers could claim the same row.
Not currently reachable: hallu-zarr.sh takes an exclusive flock and is the only caller, so the drain is serialized by construction. The risk is entirely latent, and the docstring is the actual defect: it states a guarantee the code does not provide, so a future second caller would be added on a false premise.
Either wrap the claim in BEGIN IMMEDIATE and make the docstring true, or correct the docstring to say the serialization comes from the caller's flock.
Activity
Zarr: scratch-sweep guard, probe code, claim (#1221)
neuromechanist commentedon Sep 3, 2026
Fixed in #1221 (dev commit 1867c27); ships with the next dev to main release.