Recordsgolanggoogle.golang.org/appenginev1.2.0
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
Showing the environments with the most evidence.
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 3✓ — Verified: CONTRACT 9✓
|
LOW | 4 +3 | 9 | 100% | 1 · 1✓ | 2026-10-19 |
| go 1.26 · Go · go · linux glibc
Observations: PROJECT_COMPILE 1✓ 1✕ · PROJECT_PROCESS 12✓ · PROJECT_RESOLVE 0✓ 2✕ — Usage: USED 20✓
|
LOW | 16 +20 | 0 | 81% | 1 | 2026-10-17 |
Recent failure clusters
-
observed PROJECT_RESOLVE exit 1 ×1 v1.2.0 os=linux · runtime=go@1.26 sha256:2e60e3be5c63…github.com/golang/protobuf@v1.2.0: missing go.sum entry for go.mod file; to add it:go/module · resolve-diagnostic · outer goEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-17 · Last seen: 2026-10-17
-
observed PROJECT_RESOLVE exit 1 ×1 v1.2.0 os=linux · runtime=go@1.26 sha256:34fd3bdbe7d3…go: google.golang.org/appengine@v1.2.0: missing go.sum entry for go.mod file; to add it:go/module · resolve-diagnostic · outer goEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-17 · Last seen: 2026-10-17
-
observed PROJECT_COMPILE exit 1 ×1 v1.2.0 os=linux · runtime=go@1.26 google.golang.org/appengine.APICall sha256:d84ba7d345ad…test/contract.go:<n>:<n>: cannot use func(ctx context.Context, service, method string, in, out interface{Reset(); String() string; ProtoMessage()}) error {…} …go/compiler · compiler-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-17 · Last seen: 2026-10-17
Symbols
- google.golang.org/appengine.APICall 1 1 of 1 runs passed
- google.golang.org/appengine.BackgroundContext 1 1 of 1 runs passed
- google.golang.org/appengine.MultiError.Error 2
- google.golang.org/appengine.GeoPoint 1 1 of 1 runs passed
- google.golang.org/appengine.IsDevAppServer 2 1 of 1 runs passed
- google.golang.org/appengine.IsOverQuota 1 1 of 1 runs passed
- google.golang.org/appengine.IsTimeoutError
- google.golang.org/appengine.MultiError 1
- google.golang.org/appengine.Namespace 2
- appengine.GeoPoint.Valid 1 1 of 1 runs passed
- google.golang.org/appengine.WithAPICallFunc
Published samples
- google.golang.org/appengine v1.2.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. HOW MIT-0 · 2026-10-17