Recordsgolanggithub.com/rcrowley/go-metricsfailure issue
Failure signature
PROJECT_PROCESS ERR_ASSERTION Evidence gap ×6
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-26 · Last seen: 2026-08-27
Where it was measured
PASS means the release recorded a passing observation at PROJECT_PROCESS and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v0.0.0-20250401214520-65e299d6c5c9 PASS 23 passing observations
- v0.0.0-20201227073835-cf1acfcdf475 FAIL
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×6 2026-08-26 → 2026-08-27
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last failing release v0.0.0-20201227073835-cf1acfcdf475 → first passing release v0.0.0-20250401214520-65e299d6c5c9
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/rcrowley/go-metrics v0.0.0-20201227073835-cf1acfcdf475: register and update counter and meter in a go-metrics registry This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWmetrics.NewCountermetrics.NewMetermetrics.NewRegistry MIT-0 · 2026-08-27