Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix several scan storage issues #7584

Closed
wants to merge 7 commits into from
Closed

Conversation

sschuberth
Copy link
Member

Please have a look at the individual commit messages for the details.

The latest tag is more likely to have stored scan results in
ClearlyDefined.

Signed-off-by: Sebastian Schuberth <[email protected]>
Esp. when passing scan storage configuration via command line options
while other storage may be configured in the global `config.yml` it can
be beneficial to know what exactly takes effect.

Signed-off-by: Sebastian Schuberth <[email protected]>
Emphasize that this is about matching results, not any results.

Signed-off-by: Sebastian Schuberth <[email protected]>
This override was not taking into account the `ScannerCriteria` at all,
so the default implementation should be used instead.

Signed-off-by: Sebastian Schuberth <[email protected]>
@sschuberth sschuberth requested a review from a team as a code owner September 27, 2023 10:00
ClearlyDefined returns VCS URLs like [1] which makes the provenance
matcher fail as it checks for [2] (plus the revision independently).
Properly parse the VCS URL returned by ClearlyDefined to fix this.

[1]: https://github.com/vdurmont/semver4j/tree/88912638db3f6112a2b345f1638ced33a0a606e1
[2]: https://github.com/vdurmont/semver4j.git

Signed-off-by: Sebastian Schuberth <[email protected]>
Previously, the empty `scanResults` were used in log output. Refactor
code to avoid that error.

Signed-off-by: Sebastian Schuberth <[email protected]>
@sschuberth sschuberth force-pushed the scan-storage-mismatch-logging branch from 5f04640 to 47a2fbb Compare September 27, 2023 10:07
@codecov
Copy link

codecov bot commented Sep 27, 2023

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (902bfef) 68.03% compared to head (47a2fbb) 68.04%.

Additional details and impacted files
@@            Coverage Diff            @@
##               main    #7584   +/-   ##
=========================================
  Coverage     68.03%   68.04%           
+ Complexity     2023     2022    -1     
=========================================
  Files           344      344           
  Lines         16727    16721    -6     
  Branches       2371     2369    -2     
=========================================
- Hits          11381    11378    -3     
  Misses         4363     4363           
+ Partials        983      980    -3     
Flag Coverage Δ
funTest-docker 69.40% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Coverage Δ
.../src/main/kotlin/storages/ClearlyDefinedStorage.kt 85.22% <ø> (+2.24%) ⬆️

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@sschuberth sschuberth marked this pull request as draft September 27, 2023 11:00
@sschuberth
Copy link
Member Author

sschuberth commented Sep 27, 2023

Superseded by multiple smaller PRs.

@sschuberth sschuberth closed this Sep 27, 2023
@sschuberth sschuberth deleted the scan-storage-mismatch-logging branch September 27, 2023 17:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant