fix(version): do not cache a comparator that failed to build#3567
Open
arpitjain099 wants to merge 1 commit into
Open
fix(version): do not cache a comparator that failed to build#3567arpitjain099 wants to merge 1 commit into
arpitjain099 wants to merge 1 commit into
Conversation
Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
getComparatorcaches the constructed comparator inv.comparators[format]unconditionally, including when construction returned an error:On a parse failure the constructor returns a zero-value comparator (for Semantic/JVM/Bitnami its internal
*hashiVer.Versionis nil) together with an error. Caching it means the next lookup for that format hits the cache and returns it with anilerror, so the caller proceeds toCompare, which dereferences the nil version and panics. For formats without a pointer it silently compares against an empty version, i.e. a false negative in matching.The map persists across calls once a pointer-receiver entry point (
Is/Validate) populates it, so a repeated comparison on the same*Versiontriggers it. In-tree this is reachable frommatcher/rpm/rhel_eus.goneededFixes, which callsv.Is(LT, ...)in a loop on the same package version.Repro:
The fix returns early on a build error so the broken comparator is never cached, and the error surfaces consistently instead. Added a regression test.
go test ./grype/version/passes.