Skip to content
quarry Ambiguous Artifact ID
Login

Ambiguous Artifact ID

The artifact hash prefix 0cb74 is ambiguous and might mean any of the following:

  1. 0cb7422082bd74e0dd6f5331628bdb373f6f88903994f57b2b574f22f3cc61eb -

  2. 0cb74f5e4dc188770a4b0e26c3392604c3ff17c603016658d3f1fed72f14a466 -

    • File cmd/quarry/main.go — part of check-in [4a479e6ce2] at 2026-08-18 01:15:43 on branch trunk — api: make the repo set a concurrent registry; serve rejects positionals

      Deps.Repos was a bare map, read by every op on the request path and written only at startup. Adding repositories at runtime — the point of the registry ticket — makes that a data race with no symptom until it corrupts one. api.Repos owns the lock; a *Repo is published complete or not at all, and Delete hands back the entry so the caller can close the index and stop the pipeline.

      serve now refuses leftover arguments. Go's flag package stops at the first non-flag and returns the rest, so one unquoted shell variable silently dropped twelve --repo flags and quarry served the remaining eleven without a word. (user: dmestas, size: 42244) [annotate] [blame] [check-ins using]