Records/golang/github.com/Azure/azure-pipeline-go/v0.2.1/github.com/Azure/azure-pipeline-go/pipeline.Response

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 PROJECT_RESOLVE exit 2 ×1 v0.2.1 os=linux · runtime=go@1.26 sha256:2b5706b57a17…
  github.com/mattn/go-ieproxy@v0.0.0-20190610004146-91bb50d98149: missing go.sum entry for go.mod file; to add it:
  go/module · resolve-diagnostic · outer go
  Evidence quality: complete · Environment variants: 1 · First recorded: 2026-10-23 · Last seen: 2026-10-23
  Where does this failure start and stop?
• observed PROJECT_RESOLVE exit 1 ×1 v0.2.1 os=linux · runtime=go@1.26 sha256:d0100fc48b62…
  go: github.com/Azure/azure-pipeline-go@v0.2.1: missing go.sum entry for go.mod file; to add it:
  go/module · resolve-diagnostic · outer go
  Evidence quality: complete · 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 v0.2.1 os=linux · runtime=go@1.26 github.com/Azure/azure-pipeline-go/pipeline.Response sha256:063b70d32c72…
  panic: unexpected log entries: [5:outer-info · ] · goroutine 1 [running]: · main.main()
  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?