-
Notifications
You must be signed in to change notification settings - Fork 979
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
[Bug]: Slither detects already triaged results #1965
Comments
I have the same issue, I hide all results by run triage mode and all saved in slither.db.json, however when I run slither again and again, each time gives me the issues and every run give me different result |
@amrshaban2005 Is it also with the divide before multiply detector or a different one? |
@0xalpharush no, it happens with many different detectors like reentrancy-no-eth, unchecked-transfer, unused-return....etc |
@0xalpharush Could you kindly provide me with any updates, please? |
@amrshaban2005 hi, i can't reproduce this issue with other detectors. Please add some more details or better a code to reproduce it. Thank you. |
hi, thank you for follow up, our code base is complicated so can't write a simple code to reproducer it ,
please note that every time run |
Closed by #2114 |
Describe the issue:
Slither seems to be detecting issues that have already been triaged into the
slither.db.json
from time to time.This makes it difficult to get consistent results between runs after triaging findings, and also generates false positives when running Slither in CI.
This could be related to the ID of the findings that is stored in the DB file, which seems to vary between runs.
Code example to reproduce the issue:
Public sample to reproduce the issue with instructions here: balancer/balancer-v2-monorepo#2514.
Version:
0.9.3
Relevant log output:
The text was updated successfully, but these errors were encountered: