-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
SBOM generation tool fails during gitignore filtering for libraries with no files #122044
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
Comments
Looks like this is not a security issue, just a bug. |
I guess that all of the SBOM-related issues are actually related to type-security label. |
We can change the labeling scheme if it makes it less confusing! :) |
I was under the impression that |
…pythonGH-122045) (cherry picked from commit 4e04d1a) Co-authored-by: Seth Michael Larson <[email protected]>
…pythonGH-122045) (cherry picked from commit 4e04d1a) Co-authored-by: Seth Michael Larson <[email protected]>
GH-122045) (#122354) Co-authored-by: Seth Michael Larson <[email protected]>
GH-122045) (#122355) Co-authored-by: Seth Michael Larson <[email protected]>
Merged and backported, thanks! |
Within #119316 the libb2 library was removed. When running the SBOM generation tool a confusing error is raised during gitignore filtering instead of triggering the helpful error for the "no files for package" condition. This can be avoided by short-circuiting gitignore filtering when no files are present.
Linked PRs
The text was updated successfully, but these errors were encountered: