Recordsgolanggithub.com/jackc/pgiofailure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
test/contract.go:<n>:<n>: undefined: pgproto3.AuthenticationResponse
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-09-14 · Last seen: 2026-09-14
sha256:fbcd3e8fd1fc…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v1.0.0 FAIL
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-14 → 2026-09-14
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.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_COMPILE.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/jackc/pgio v1.0.0: SetInt32 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. HOWgithub.com/jackc/pgio.SetInt32go 1.26.6 MIT-0 · 2026-08-26
- github.com/jackc/pgio v1.0.0: AppendUint64 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. HOWgithub.com/jackc/pgio.AppendUint64go 1.26.6 MIT-0 · 2026-08-26
- github.com/jackc/pgio v1.0.0: AppendUint32 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. HOWgithub.com/jackc/pgio.AppendUint32 MIT-0 · 2026-08-26