Recordsgolanggithub.com/jackc/pgproto3/v2v2.1.1github.com/jackc/pgproto3/v2.NewBackend
OS × runtime at a glance
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Published samples
- 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
Compatibility matrix
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| go 1.26 · Go · go · linux glibc · docker
Observations: PROJECT_TEST 2✓ — Verified: CONTRACT 1✓
|
LOW | 2 | 1 | 100% | 1 · 1✓ | 2026-09-17 |
| go 1.26 · Go · go · linux glibc
Observations: PROJECT_COMPILE 0✓ 3✕ · PROJECT_PROCESS 16✓ — Verified: UNKNOWN 0✓ 2✕
|
LOW | 19 | 2 | 76% | 1 | 2026-09-14 |
snapshot · 2026-09-17
Failure clusters
-
observed UNKNOWN exit 1 ERROR Evidence gap ×2 v2.1.1 os=linux · runtime=go@1.26 github.com/jackc/pgproto3/v2.NewBackend sha256:48372bc6eceb…go: downloading github.com/jackc/pgmock v0.0.0-20210724152146-4ad1a8207f65 · go: downloading github.<token> v2.0.1 …go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-14 · Last seen: 2026-09-14Diagnostic re-verification candidate
-
observed PROJECT_COMPILE exit 1 ×1 v2.1.1 os=linux · runtime=go@1.26 github.com/jackc/pgproto3/v2.NewBackend sha256:a0e1c511de91…test/contract.go:<n>:<n>: assignment mismatch: 2 variables but sm.Encode returns 1 value …go/compiler · compiler-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-14 · Last seen: 2026-09-14
-
observed PROJECT_COMPILE exit 1 ×1 v2.1.1 os=linux · runtime=go@1.26 github.com/jackc/pgproto3/v2.NewBackend sha256:fbcd3e8fd1fc…test/contract.go:<n>:<n>: undefined: pgproto3.AuthenticationResponsego/compiler · compiler-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-14 · Last seen: 2026-09-14
-
observed PROJECT_COMPILE exit 1 ×1 v2.1.1 os=linux · runtime=go@1.26 github.com/jackc/pgproto3/v2.NewBackend sha256:5dbb94925efc…<path> assignment mismatch: 2 variables but query.Encode returns 1 valuego/compiler · compiler-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-14 · Last seen: 2026-09-14