Recordsgolanggithub.com/jackc/pgproto3/v2failure 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…
github.com/jackc/pgproto3/v2.AuthenticationOk github.com/jackc/pgproto3/v2.AuthenticationResponse github.com/jackc/pgproto3/v2.BackendMessage github.com/jackc/pgproto3/v2.NewBackend github.com/jackc/pgproto3/v2.NewChunkReader github.com/jackc/pgproto3/v2.NewFrontend
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.
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.
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 | v2.3.3 | v2.1.1 |
|---|---|---|
| github.com/jackc/chunkreader/v2 | v2.0.1 | v2.0.0 |
| github.com/stretchr/testify | v1.8.1 | v1.4.0 |
| github.com/jackc/pgio | v1.0.0 | v1.0.0 |
Moved: 2 · unchanged at every release: 1
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
- No release in this window recorded a passing observation at PROJECT_COMPILE.
- Releases in this window never measured at PROJECT_COMPILE: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/jackc/pgproto3/v2 v2.1.1: NewBackend 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/pgproto3/v2.NewBackend MIT-0 · 2026-09-14
- github.com/jackc/pgproto3/v2 v2.1.1: AuthenticationOk 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/pgproto3/v2.AuthenticationOk MIT-0 · 2026-09-14
- github.com/jackc/pgproto3/v2 v2.1.1 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. HOW MIT-0 · 2026-09-14