Records/golang/golang.org/x/tools/v0.50.0

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.

Recent failure clusters

• observed UNKNOWN exit 1 ERROR Evidence gap ×2 v0.50.0 os=linux · runtime=go@1.26 sha256:825e05b09b71…
  verifying modernc.org/mathutil@v1.6.0/go.mod: checksum mismatch · downloaded: h1:<token> · go.sum: h1:<token> · SECURITY ERROR
  go · unclassified-diagnostic · outer go mod · gap stage-unknown
  Evidence quality: complete · Environment variants: 1 · First recorded: 2026-09-19 · Last seen: 2026-09-19
  Diagnostic re-verification candidate
  Where does this failure start and stop?
• observed PROJECT_RESOLVE exit 1 ×1 v0.50.0 os=linux · runtime=go@1.26 sha256:4886dbf7feaf…
  <path> missing go.sum entry for module providing package golang.org/x/sync/errgroup (imported by golang.org/x/tools/go/packages); to add:
  go/module · resolve-diagnostic · outer go run
  Evidence quality: complete · Environment variants: 1 · First recorded: 2026-09-19 · Last seen: 2026-09-19
  Where does this failure start and stop?
• observed PROJECT_RESOLVE exit 1 ×1 v0.50.0 os=linux · runtime=go@1.26 sha256:a43a1d0fc542…
  <path>:<n>:<n>: missing go.sum entry for module providing package golang.org/x/sys/unix (imported by modernc.org/ccgo/v3/lib); to add: …
  go/module · resolve-diagnostic · outer go run
  Evidence quality: complete · Environment variants: 1 · First recorded: 2026-09-19 · Last seen: 2026-09-19
  Where does this failure start and stop?

Symbols

No symbols with evidence yet.