Recordsgolanggithub.com/jackc/puddlev1.3.0
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
| debian glibc | ubuntu glibc | |
|---|---|---|
| github.com/jackc/puddle.ErrClosedPool | 100%2 | 100%4 |
| github.com/jackc/puddle.ErrNotAvailable | 100%2 | |
| github.com/jackc/puddle.NewPool | 100%4 | |
| github.com/jackc/puddle.Pool | 100%2 |
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.
Environment detail
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
Usage: USED 1✓
|
LOW | 0 +1 | 0 | — | 1 | 2026-09-03 |
| go 1.26 · Go · go · linux glibc · docker
Observations: PROJECT_LOAD 2✓ · PROJECT_TEST 2✓ — Usage: USED 4✓ — Verified: CONTRACT 2✓
|
LOW | 4 +4 | 2 | 100% | 1 · 1✓ | 2026-09-17 |
| go 1.26 · Go · go · linux glibc
Observations: PROJECT_PROCESS 4✓ — Usage: USED 6✓ — Verified: UNKNOWN 0✓ 1✕
|
LOW | 4 +6 | 1 | 80% | 1 | 2026-09-16 |
Recent failure clusters
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.3.0 os=linux · runtime=go@1.26 github.com/jackc/puddle.ErrClosedPool sha256:9fe0e5655146…assertion 5 failed: destructor not called properly · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-16 · Last seen: 2026-09-16Diagnostic re-verification candidate
Symbols
- github.com/jackc/puddle.ErrClosedPool 1 1 of 2 runs passed
- github.com/jackc/puddle.ErrNotAvailable 0 of 1 runs passed
- github.com/jackc/puddle.NewPool 0 of 1 runs passed
- github.com/jackc/puddle.Pool
Published samples
- github.com/jackc/puddle v1.3.0 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 1.26.6 MIT-0 · 2026-09-16