CodeSampleX

Recordsgolanggithub.com/google/gopacketfailure issue

Failure signature

PROJECT_RESOLVE exit 1 ×1

test/contract.go:<n>:<n>: missing go.sum entry for module providing package github.com/google/gopacket (imported by sample/test); to add: …

Evidence quality: complete · go/module · resolve-diagnostic · outer go run · First recorded: 2026-09-04 · Last seen: 2026-09-04

sha256:d36788dbbc60…

github.com/google/gopacket.Default github.com/google/gopacket.Lazy github.com/google/gopacket.NewPacket github.com/google/gopacket.NewSerializeBuffer github.com/google/gopacket.NoCopy github.com/google/gopacket.Payload github.com/google/gopacket.SerializeLayers github.com/google/gopacket.SerializeOptions github.com/google/gopacket/layers.Ethernet github.com/google/gopacket/layers.EthernetTypeIPv4 github.com/google/gopacket/layers.IPProtocolUDP github.com/google/gopacket/layers.IPv4 github.com/google/gopacket/layers.LayerTypeEthernet github.com/google/gopacket/layers.LayerTypeIPv4 github.com/google/gopacket/layers.LayerTypeUDP github.com/google/gopacket/layers.UDP github.com/google/gopacket/layers.UDPPort

Where it was measured

PASS means the release recorded a passing observation at PROJECT_RESOLVE 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