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

fields are not identical between scans in maven #2463

Closed
tomerse-sg opened this issue Jan 2, 2024 · 2 comments
Closed

fields are not identical between scans in maven #2463

tomerse-sg opened this issue Jan 2, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@tomerse-sg
Copy link

What happened:
I'm scanning some private image I have containing jars. I scanned once and got the results, and after that scanned again and some of the data was changed (even though I didn't change the image).
What you expected to happen:
the exact same results.
Steps to reproduce the issue:
scan an image with jars twice
run diff between json outputs (syft-output).
Anything else we need to know?:
I had a similar issue a while ago which I reported and was resolved for a while. maybe something changed between upgrades in syft.
I can't share the image itself but I can share the diff results:
image

Please let me know If you need any additional information.

Thanks!

Environment:

  • Output of syft version: 0.98.0
  • OS (e.g: cat /etc/os-release or similar): maxOS
@tomerse-sg tomerse-sg added the bug Something isn't working label Jan 2, 2024
@tgerla
Copy link
Contributor

tgerla commented Jan 4, 2024

Hi @tomerse-sg, thank you for the report. We are actually aware of this issue and we're tracking it here: #2405 -- we will hopefully get a fix together soon.

@wagoodman wagoodman moved this to Backlog in OSS Jan 4, 2024
@kzantow
Copy link
Contributor

kzantow commented Jul 30, 2024

I believe this should be fixed in the latest version of Syft 1.10.0, there was an issue identified and fixed, so I'm going to close this issue as I think it's a duplicate of #2967. Please let us know if you still see issues with nondeterminism.

@kzantow kzantow closed this as not planned Won't fix, can't repro, duplicate, stale Jul 30, 2024
@github-project-automation github-project-automation bot moved this from Backlog to Done in OSS Jul 30, 2024
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
Archived in project
Development

No branches or pull requests

3 participants