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

Possible to mark errors as acknowledged? #78

Open
mpeyfuss opened this issue Feb 28, 2024 · 1 comment
Open

Possible to mark errors as acknowledged? #78

mpeyfuss opened this issue Feb 28, 2024 · 1 comment

Comments

@mpeyfuss
Copy link

I love the extension for vscode! It works great. There are a few detectors that come up as false alerts. Mainly, it happens for two scenarios:

  1. Doesn't recognize the nonReentrant modifier from OZ as stopping reentrancy
  2. Misreading an OZ IERC721 interaction as an ERC-20 interaction.

I don't mind the false detections coming up tbh, it's better to verify these, but it would be great to be able to mark as ack or resolved so that my files aren't marked as filled with errors.

Happy to discuss more or show how to replicate!

@michprev
Copy link
Member

Hi @mpeyfuss, glad you like the extension!

You can disable/acknowledge errors using the // wake-disable- comments syntax. You can find the full description in the extension README or in the Wake documentation.

Regarding the false positives:

  1. Detecting reentrancy guard is non-trivial and might lead to false negatives (i.e. a missed detection). I agree we could at least try to detect the nonReentrant modifier using its name. Will consider that.
  2. Which detector reports these false positives? Is it unsafe-erc20-call or incorrect-interface?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants