Records/golang/github.com/grpc-ecosystem/grpc-gateway/v1.16.0/github.com/grpc-ecosystem/grpc-gateway/utilities.OpCapture

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-10-23

Failure clusters

• observed UNKNOWN exit 1 Evidence gap ×2 v1.16.0 os=linux · runtime=go@1.26 github.com/grpc-ecosystem/grpc-gateway/utilities.OpCapture 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-23 · Last seen: 2026-10-23
  Diagnostic re-verification candidate
  Where does this failure start and stop?
• observed PROJECT_TEST Evidence gap ×1 v1.16.0 executionContext=go · os=linux · runtime=go@1.26
  Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-10-23 · Last seen: 2026-10-23
  Where does this failure start and stop?
• observed UNKNOWN exit 1 Evidence gap ×1 v1.16.0 os=linux · runtime=go@1.26 sha256:03d97015f6fa…
  unexpected result for Grpc-Metadata-Custom-Header: key=<str>, ok=true · exit status 1
  go · unclassified-diagnostic · outer go run · gap stage-unknown
  Evidence quality: complete · Environment variants: 1 · First recorded: 2026-10-23 · Last seen: 2026-10-23
  Diagnostic re-verification candidate
  Where does this failure start and stop?