-
Notifications
You must be signed in to change notification settings - Fork 310
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
Scanner: Avoid returning irrelevant issues #7921
Comments
Thinking about solving this by either:
|
Do we get the affected file for such issues from the ScanCode result model or would we have to parse the error messages to try to find out if an issue belongs to a single file? |
FYI, this roughly goes into the direction of #4393. |
Finally, the following components adhere to the affected path of the issues WRT to path excludes and VCS:
Therefore, closing the issue as completed. Note that the exist code / issues stats CLI output of the |
Mind creating such an issue (if it does not exist yet) so that we do not forget about it? |
I've updated my above comment. |
The scanner might run into an issue which related only to a single file.
If an issue related to a file which not within the set of files resulting from filtering the scan result by VCS path, then
the issue should also be filtered out. This happens e.g. for TIMEOUT issues.
In this context, it makes sense to consider enabling the path excludes to silence timeouts as well.
The text was updated successfully, but these errors were encountered: