Recordsgolanggo.uber.org/zapfailure issue
Failure signature
UNKNOWN exit 1 ERROR Evidence gap ×1
go: downloading go.uber.org/zap v1.13.0 · verifying go.uber.org/zap@v1.13.0: checksum mismatch · downloaded: h1:<token> · go.sum: h1:<token>
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-09-15 · Last seen: 2026-09-15
sha256:cc6da42c69d5…
go.uber.org/zap.AtomicLevel go.uber.org/zap.Logger go.uber.org/zap.New go.uber.org/zap.NewAtomicLevelAt go.uber.org/zap/zapcore.AddSync go.uber.org/zap/zapcore.DebugLevel go.uber.org/zap/zapcore.EncoderConfig go.uber.org/zap/zapcore.ISO8601TimeEncoder go.uber.org/zap/zapcore.InfoLevel go.uber.org/zap/zapcore.Level go.uber.org/zap/zapcore.LowercaseLevelEncoder go.uber.org/zap/zapcore.NewCore go.uber.org/zap/zapcore.NewJSONEncoder go.uber.org/zap/zapcore.StringDurationEncoder go.uber.org/zap/zapcore.WarnLevel
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-15 → 2026-09-15
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | v1.27.1 | v1.27.0 | v1.26.0 | v1.13.0 |
|---|---|---|---|---|
| github.com/stretchr/testify | v1.8.1 | v1.8.1 | v1.8.1 | v1.4.0 |
| go.uber.org/goleak | v1.3.0 | v1.3.0 | v1.2.0 | — |
| go.uber.org/multierr | v1.11.0 | v1.10.0 | v1.10.0 | v1.3.0 |
| github.com/pkg/errors | — | — | — | v0.9.1 |
| go.uber.org/atomic | — | — | — | v1.5.0 |
| golang.org/x/lint | — | — | — | v0.0.0-20190930215403-16217165b5de |
| gopkg.in/yaml.v3 | v3.0.1 | v3.0.1 | v3.0.1 | — |
Moved: 3 · unchanged at every release: 4
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 3
- No failure domain was inferred for this failure.
Published answers for the affected releases
- go.uber.org/zap v1.13.0: New 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. HOWgo.uber.org/zap.New MIT-0 · 2026-09-15
- go.uber.org/zap v1.13.0: Logger 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. HOWgo.uber.org/zap.Loggergo 1.26.6 MIT-0 · 2026-09-15
- go.uber.org/zap v1.13.0: AtomicLevel 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. HOWgo.uber.org/zap.AtomicLevel MIT-0 · 2026-09-15