Records/golang/go.opentelemetry.io/otel/v1.37.0/go.opentelemetry.io/otel/attribute.BoolValue

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.

snapshot · 2026-09-16

Failure clusters

• observed PROJECT_COMPILE exit 1 EMPTY ×1 v1.37.0 os=linux · runtime=go@1.26 sha256:deba6f972850…
  test/contract.go:<n>:<n>: undefined: attribute.EMPTY
  go/compiler · compiler-diagnostic · outer go run
  Evidence quality: complete · Environment variants: 1 · First recorded: 2026-09-16 · Last seen: 2026-09-16
  Where does this failure start and stop?
• observed UNKNOWN exit 1 Evidence gap ×1 v1.37.0 os=linux · runtime=go@1.26 sha256:61579858e38a…
  # sample/test · test/contract.go:<n>:<n>: cannot call pointer method Len on <str>.Set · test/contract.go:<n>:<n>: cannot call pointer method Len on <str>.Set
  go · unclassified-diagnostic · outer go run · gap stage-unknown
  Evidence quality: complete · Environment variants: 1 · First recorded: 2026-09-16 · Last seen: 2026-09-16
  Diagnostic re-verification candidate
  Where does this failure start and stop?
• observed UNKNOWN exit 1 Evidence gap ×1 v1.37.0 os=linux · runtime=go@1.26 sha256:93a520b5395d…
  # command-line-arguments · <path> cannot call pointer method Len on <str>.Set · <path> cannot call pointer method Len on <str>.Set
  go · unclassified-diagnostic · outer go run · gap stage-unknown
  Evidence quality: complete · Environment variants: 1 · First recorded: 2026-09-16 · Last seen: 2026-09-16
  Diagnostic re-verification candidate
  Where does this failure start and stop?