Recordsgolanggithub.com/jackc/pgproto3/v2failure issue
Failure signature
UNKNOWN exit 1 ERROR Evidence gap ×2
go: downloading github.com/jackc/pgmock v0.0.0-20210724152146-4ad1a8207f65 · go: downloading github.<token> v2.0.1 …
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-09-14 · Last seen: 2026-09-14
sha256:48372bc6eceb…
github.com/jackc/pgproto3/v2.AuthenticationOk github.com/jackc/pgproto3/v2.BackendKeyData github.com/jackc/pgproto3/v2.CommandComplete github.com/jackc/pgproto3/v2.NewBackend github.com/jackc/pgproto3/v2.NewChunkReader github.com/jackc/pgproto3/v2.NewFrontend github.com/jackc/pgproto3/v2.ProtocolVersionNumber github.com/jackc/pgproto3/v2.Query github.com/jackc/pgproto3/v2.ReadyForQuery github.com/jackc/pgproto3/v2.StartupMessage github.com/jackc/pgproto3/v2.Terminate
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 ×2 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
- 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: 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