Recordsgolanggolang.org/x/sysv0.0.0-20210124154548-22da62e12c0c
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
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
Observations: PROJECT_LOAD 2✓ · PROJECT_TEST 2✓ — Usage: USED 2✓ — Verified: CONTRACT 1✓
|
LOW | 4 +2 | 1 | 100% | 1 · 1✓ | 2026-10-13 |
| go 1.26 · Go · go · linux glibc
Observations: PROJECT_PROCESS 15✓ · PROJECT_RESOLVE 0✓ 1✕ · PROJECT_TEST 1✓ — Usage: USED 10✓
|
MEDIUM | 17 +10 | 0 | 94% | 2 | 2026-09-19 |
Recent failure clusters
-
observed PROJECT_RESOLVE exit 1 ×4 v0.0.0-20190215142949-d0b11bdaac8a → v0.0.0-20210124154548-22da62e12c0c → v0.0.0-20220715151400-c0bba94af5f8 → v0.5.0 os=linux · runtime=go@1.26 sha256:626bbf4dcdcc…test/contract.go:<n>:<n>: missing go.sum entry for module providing package golang.org/x/sys/unix (imported by example.com/sample/test); to add:go/module · resolve-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-19 · Last seen: 2026-10-13
Symbols
- golang.org/x/sys/unix.ByteSliceToString
- golang.org/x/sys/unix.Getpagesize
- golang.org/x/sys/unix.Getpid
- golang.org/x/sys/unix.Uname
- golang.org/x/sys/unix.Utsname
Published samples
- golang.org/x/sys v0.0.0-20210124154548-22da62e12c0c 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-17