Recordsgolangcloud.google.com/go/pubsubv1.2.0Client.CreateTopic
Change the conditions
Current conditions
Client.CreateTopic @v1.2.0debian glibc · x64 · go 1.26 · go · go
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- 2 / 2
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-10-19
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.2.0
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:23fa82d9b00b271b9a841a72d3d9683b9676829a6b1f1ba71f554485aa561ebc
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| cloud.google.com/go | v0.52.0 | CANDIDATE Correlated change; unproven combination | contract passed | 7 project-days |
| cloud.google.com/go | v0.56.0 | CANDIDATE Correlated change; unproven combination | builds observed | 2 project-days |
| github.com/golang/protobuf | v1.3.3 | CANDIDATE Correlated change; unproven combination | contract passed | 7 project-days |
| github.com/golang/protobuf | v1.3.5 | CANDIDATE Correlated change; unproven combination | builds observed | 2 project-days |
| github.com/google/go-cmp | v0.4.0 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| golang.org/x/oauth2 | v0.0.0-20200107190931-bf48bf16ab8d | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| golang.org/x/sync | v0.0.0-20190911185100-cd5d95a43a6e | CANDIDATE Correlated change; unproven combination | contract passed | 7 project-days |
| golang.org/x/sync | v0.0.0-20200317015054-43a5402ce75a | CANDIDATE Correlated change; unproven combination | builds observed | 2 project-days |
| golang.org/x/time | v0.0.0-20191024005414-555d28b269f0 | CANDIDATE Correlated change; unproven combination | nothing measured | 9 project-days |
| google.golang.org/api | v0.15.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| google.golang.org/api | v0.17.0 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| google.golang.org/api | v0.28.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| google.golang.org/genproto | v0.0.0-20200204135345-fa8e72b47b90 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| google.golang.org/genproto | v0.0.0-20200212174721-66ed5ce911ce | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| google.golang.org/genproto | v0.0.0-20200331122359-1ee6d9798940 | CANDIDATE Correlated change; unproven combination | builds observed | 2 project-days |
| google.golang.org/grpc | v1.27.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| google.golang.org/grpc | v1.27.1 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| google.golang.org/grpc | v1.28.0 | CANDIDATE Correlated change; unproven combination | builds observed | 2 project-days |
| github.com/googleapis/gax-go/v2 | v2.0.5 | PASS All observations passed | contract passed | 9 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
Moved: 9 · unchanged at every release: 1
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Recent failure clusters
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.2.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-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-18 · Last seen: 2026-10-18Diagnostic re-verification candidate