CodeSampleX

Recordsgolangcloud.google.com/go/kmsfailure issue

Failure signature

UNKNOWN exit 1 Evidence gap ×1

go: downloading cloud.google.com/go/kms v1.34.0 · go: downloading google.golang.org/protobuf v1.36.11 …

Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-10-09 · Last seen: 2026-10-09

sha256:7c1315bc7de9…

cloud.google.com/go/kms/apiv1/kmspb.CryptoKey cloud.google.com/go/kms/apiv1/kmspb.CryptoKey_AES_WRAPPING cloud.google.com/go/kms/apiv1/kmspb.CryptoKey_CRYPTO_KEY_PURPOSE_UNSPECIFIED cloud.google.com/go/kms/apiv1/kmspb.CryptoKey_CryptoKeyPurpose cloud.google.com/go/kms/apiv1/kmspb.CryptoKey_CryptoKeyPurpose_name cloud.google.com/go/kms/apiv1/kmspb.CryptoKey_CryptoKeyPurpose_value

Where it was measured

PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

Where it reproduced

Nearest known PASS/FAIL boundaries

No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.

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: 8 · 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.

Evidence gaps

Published answers for the affected releases

Back to the package