-
Notifications
You must be signed in to change notification settings - Fork 13
Support following absolute symlinks for node analysis #1014
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
Conversation
Images are ready for the commit at bb00e04. To use the images, use the tag |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks legit to me
I will try this on Matthias'es feat branch: stackrox/stackrox#3722 |
I managed to test it only locally on Colima, here it the failure obtained using the code from stackrox/stackrox#3722 (Scanner |
Co-authored-by: Misha Sugakov <537715+msugakov@users.noreply.github.com>
@RTann: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM assuming that we handle the panic when exploring the filesystem on Docker in a separate PR.
…er into ross/node-analyze-symlink
I'm going to merge because I think they are somewhat unrelated and can be handled in separate PRs. Plus, this is not used in prod yet |
No description provided.