CodeSampleX

Recordsgolanggithub.com/grpc-ecosystem/grpc-gatewayfailure issue

Failure signature

UNKNOWN exit 1 Evidence gap ×2

go: build output <str> already exists and is a directory

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

sha256:0882784d80c2…

github.com/grpc-ecosystem/grpc-gateway/runtime.DefaultHeaderMatcher github.com/grpc-ecosystem/grpc-gateway/runtime.ErrInvalidPattern github.com/grpc-ecosystem/grpc-gateway/runtime.ErrNotMatch github.com/grpc-ecosystem/grpc-gateway/runtime.JSONBuiltin github.com/grpc-ecosystem/grpc-gateway/runtime.NewPattern github.com/grpc-ecosystem/grpc-gateway/runtime.NewServeMux github.com/grpc-ecosystem/grpc-gateway/utilities.NewDoubleArray github.com/grpc-ecosystem/grpc-gateway/utilities.OpCapture github.com/grpc-ecosystem/grpc-gateway/utilities.OpLitPush github.com/grpc-ecosystem/grpc-gateway/utilities.OpPush

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.

Evidence gaps

Published answers for the affected releases

Back to the package