You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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 methodRelativeFileByPath
.Environment:
syft version
:syft 1.19.0
cat /etc/os-release
or similar): MacOSThe text was updated successfully, but these errors were encountered: