fix: Archive extraction path correctly points to the jar file that's being extracted #407
+27
−2
Conversation
This file contains 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
oliverchang
approved these changes
Jan 23, 2025
erikvarga
reviewed
Jan 23, 2025
| @@ -276,7 +276,7 @@ func (e Extractor) extractWithMax(ctx context.Context, input *filesystem.ScanInp | |||
| GroupID: pp.GroupID, | |||
| SHA1: sha1, | |||
| }, | |||
| Locations: []string{path}, | |||
| Locations: []string{input.Path, path}, | |||
There was a problem hiding this comment.
Make sure to update the tests too
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.
Currently archive extractor saves the path within the jar file (appended to the jar file path) as the Location of the inventory, which is a path that does not exist on disk.
This moves it to a secondary location, so the first location is a real path.