From 1b3698334adb6290956fc6735217e3f9616bbb08 Mon Sep 17 00:00:00 2001 From: Alex Eagle Date: Thu, 17 Jul 2025 10:22:22 -0700 Subject: [PATCH] gazelle_manifest: print the wrong hash when encountered Ideally developers should always re-run the manifest generator, which will update the hash for them. However I've got clients where the CI system is the only place that all the dependencies can resolve, either because of credentials needed to access the wheelhouse/PyPI, or because of disk exhaustion from massive wheels. Printing the difference allows a red PR to be greened up just by reading the CI log. --- gazelle/manifest/manifest.go | 3 +++ 1 file changed, 3 insertions(+) diff --git a/gazelle/manifest/manifest.go b/gazelle/manifest/manifest.go index 26b0dfb394..c5cd8a7d69 100644 --- a/gazelle/manifest/manifest.go +++ b/gazelle/manifest/manifest.go @@ -70,6 +70,9 @@ func (f *File) VerifyIntegrity(manifestGeneratorHashFile, requirements io.Reader return false, fmt.Errorf("failed to verify integrity: %w", err) } valid := (f.Integrity == fmt.Sprintf("%x", integrityBytes)) + if (!valid) { + fmt.Printf("WARN: Integrity hash was %v but expected %x\n", f.Integrity, integrityBytes) + } return valid, nil }