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

Path curations with "/" in the Path leads to empty license findings in scan results #9712

Open
MNesche opened this issue Jan 9, 2025 · 0 comments
Assignees
Labels
bug Issues that are considered to be bugs scanner About the scanner tool

Comments

@MNesche
Copy link

MNesche commented Jan 9, 2025

Describe the bug

A VCS path curation in a curation file with "/" in the Path leads to empty license findings in scan results.
This behaviour seems to be MS Windows specific.

To Reproduce

Steps to reproduce the behavior:

  1. Create a path curation with the path leading to a subdirectory within the repository, i.e. "ext/filtering"
  2. Run the analyzer and scanner
  3. Check the scan results
  4. Setting the path curation for the main directory, i.e. just "ext", shows all scan results, including those in the previously set subdirectory.

Expected behavior

There should be scan results for the content in the subdirectory of the repository.

Console / log output

No output.

Environment

MS Windows 10

Additional context

After a couple of checks, also with a result when running on Linux, this seems to be a path-separator issue of ORT when running on Windows.
Until there's a fix available, the only workaround is to use only one directory and use package configurations path excludes for the others.
Example-Path: "modules/core"
Use just "modules" in the curation and add path excludes for any other directory beyond that, except "core".

@MNesche MNesche added bug Issues that are considered to be bugs to triage Issues that need triaging labels Jan 9, 2025
@sschuberth sschuberth added scanner About the scanner tool and removed to triage Issues that need triaging labels Jan 9, 2025
@sschuberth sschuberth self-assigned this Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issues that are considered to be bugs scanner About the scanner tool
Projects
None yet
Development

No branches or pull requests

2 participants