Initialize sbomSet when nil instead of error

[matthyx]

Fixes #304
This is safe to do after ensuring kubescape/kubevuln#339

Summary by CodeRabbit

• Bug Fixes
  • Improved error resilience by gracefully initializing default values instead of returning errors in edge cases.

[coderabbitai]

📝 Walkthrough

Walkthrough

The change modifies error handling in the dynamic path detector to proceed with an empty set when SBOM data is unavailable, instead of returning an error. This enables dynamic path compression to execute even without SBOM information.

Changes

Cohort / File(s)	Summary
Dynamic Path Detector pkg/registry/file/dynamicpathdetector/analyze_opens.go	Removed errors import and replaced nil-check error return with initialization of empty thread-unsafe set, allowing the detector to proceed when SBOM is missing.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related issues

• Dynamic path compression bypassed when SBOM is missing #304: This PR directly addresses the root cause described in the issue by enabling dynamic path compression to run when SBOM is not available, preventing profiles from being marked as too-large when dealing with high file I/O workloads.

Poem

🐰 No more heartbreak when SBOM's away,
Dynamic paths compress! Hip-hip-hooray!
Empty sets flow where errors once stood,
Millions collapse to thousands—so good! ✨
Lucene files bow down, compression's the way!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately reflects the main change: initializing sbomSet when nil instead of returning an error, which is the core fix in the pull request.
Linked Issues check	✅ Passed	The pull request implements the proposed fix from issue #304 by initializing sbomSet to an empty set when nil instead of returning an error, enabling dynamic path compression to run even without SBOM data.
Out of Scope Changes check	✅ Passed	All changes are directly scoped to fixing issue #304; the modification to analyze_opens.go only changes the nil-handling behavior as required by the issue.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix-304

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Summary:

• License scan: failure
• Credentials scan: failure
• Vulnerabilities scan: failure
• Unit test: success
• Go linting: failure