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

go-module-file-cataloger fails if symlinks in path #3614

Open
Silvanoc opened this issue Jan 23, 2025 · 0 comments
Open

go-module-file-cataloger fails if symlinks in path #3614

Silvanoc opened this issue Jan 23, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@Silvanoc
Copy link

What happened:

Scanning a directory containing a Go project results in the go-module-file-cataloger failing to properly resolve the path. As a result it fails to report the h1 digests of the Go dependencies and reports the warning [0000] WARN unable to build link resolution index for filetree search context error=unable to get node for path="xyz": cycle during symlink resolution.

What you expected to happen:

Scan reporting same results no matter if symlinks are in the path or not.

Steps to reproduce the issue:

Scan the same Go project with and without symlinks in the path and compare results.

Anything else we need to know?:

If I have diagnosed it right, the issue comes from the go-module-file-cataloger implementation of the method RelativeFileByPath.

Environment:

  • Output of syft version: syft 1.19.0
  • OS (e.g: cat /etc/os-release or similar): MacOS
@Silvanoc Silvanoc added the bug Something isn't working label Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: No status
Development

No branches or pull requests

1 participant