Records/golang/cloud.google.com/go/v0.52.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 Evidence gap ×1 v0.52.0 os=linux · runtime=go@1.26 sha256:0882784d80c2…
  go: build output <str> already exists and is a directory
  go · unclassified-diagnostic · outer go build · gap stage-unknown
  Evidence quality: complete · Environment variants: 1 · First recorded: 2026-10-18 · Last seen: 2026-10-18
  Diagnostic re-verification candidate
  Where does this failure start and stop?
• observed UNKNOWN exit 1 Evidence gap ×1 v0.52.0 os=linux · runtime=go@1.26 sha256:23fa82d9b00b…
  panic: runtime error: invalid memory address or nil pointer dereference · [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x783c57] …
  go · unclassified-diagnostic · outer go run · gap stage-unknown
  Evidence quality: complete · Environment variants: 1 · First recorded: 2026-10-18 · Last seen: 2026-10-18
  Diagnostic re-verification candidate
  Where does this failure start and stop?
• observed UNKNOWN exit 1 Evidence gap ×1 v0.52.0 os=linux · runtime=go@1.26 sha256:8323d5d2a0e9…
  expected nil error for struct, got: bigquery: field <str> of type bigquery.NullString: use <str> only for []byte and struct pointers; for all other types, use …
  go · unclassified-diagnostic · outer go run · gap stage-unknown
  Evidence quality: complete · Environment variants: 1 · First recorded: 2026-10-18 · Last seen: 2026-10-18
  Diagnostic re-verification candidate
  Where does this failure start and stop?

Symbols

No symbols with evidence yet.