Recordsgolanggolang.org/x/toolsv0.31.0golang.org/x/tools/go/ast/astutil.Apply
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
- golang.org/x/tools v0.31.0: astutil.Apply 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. HOWgolang.org/x/tools/go/ast/astutil.Apply MIT-0 · 2026-08-27
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
Observations: PROJECT_PROCESS 4✓
|
LOW | 4 | 0 | 100% | 1 | 2026-08-29 |
| go 1.26 · Go · go · linux musl · docker
Verified: CONTRACT 1✓
|
LOW | 0 | 1 | 100% | 0 · 1✓ | 2026-08-27 |
snapshot · 2026-08-31
Failure clusters
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×7 v0.1.10 → v0.31.0 os=linuxEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-26 · Last seen: 2026-08-27Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×6 v0.1.10 → v0.31.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:9be950af9140…Traceback (most recent call last): · File <str>, line 1, in <module> · ModuleNotFoundError: No module named <str>python3 · unclassified-diagnostic · outer python3 · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×5 v0.1.10 → v0.31.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:91ad26545eb1…node:internal/modules/cjs/loader:<n> · throw err; · ^ · Error: Cannot find module <str>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×3 v0.1.10 → v0.31.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:72ba2d1e946f…<path>: No module named pippython3 · unclassified-diagnostic · outer python3 · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed PROCESS_START process start failed Evidence gap ×2 v0.31.0 → v0.36.0 executionContext=node · os=linux · runtime=node@22.23 sha256:c12549970456…· structured-termination · gap diagnostic-missingEvidence quality: partial · Environment variants: 2 · First recorded: 2026-08-30 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×2 v0.31.0 os=linux · runtime=go@1.26 sha256:e148632e8429…panic: runtime error: invalid memory address or nil pointer dereference · [signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x783bfc] …go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed PROJECT_RESOLVE exit 1 ×1 v0.31.0 os=linux · runtime=go@1.26 sha256:dbe026e304ff…test/contract.go:<n>:<n>: missing go.sum entry for module providing package golang.org/x/tools/txtar (imported by example.com/sample/test); to add:go/module · resolve-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29
-
observed UNKNOWN exit 1 Evidence gap ×1 v0.31.0 os=linux · runtime=go@1.26 sha256:23ccd0c7b557…FAIL: expected 168h for 1w, got 0s (err: time: unknown unit <str> in duration <str>) · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v0.31.0 os=linux · runtime=go@1.26 sha256:2470d64a481a…# example.com/sample/test · test/contract.go:<n>:<n>: dur.UnmarshalText undefined (type caddy.Duration has no field or method UnmarshalText)go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v0.31.0 os=linux · runtime=go@1.26 sha256:31bc65941ca5…# example.com/sample/test · test/contract.go:<n>:<n>: dur.String undefined (type caddy.Duration has no field or method String) …go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30Diagnostic re-verification candidate
-
observed PROCESS_START process start failed Evidence gap ×1 v0.31.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:2617e70290c8…pytest · structured-termination · outer pytest · gap diagnostic-missingEvidence quality: partial · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed PROJECT_COMPILE exit 1 ×1 v0.31.0 os=linux · runtime=go@1.26 sha256:558314b686cc…<path> undefined: certmagic.ACMETLS1Protocolgo/compiler · compiler-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31
Showing the 12 most-reported of 27 recorded failure clusters. The rest are single reports.