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
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:
Doesn't recognize the nonReentrant modifier from OZ as stopping reentrancy
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!
The text was updated successfully, but these errors were encountered:
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:
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.
Which detector reports these false positives? Is it unsafe-erc20-call or incorrect-interface?
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:
nonReentrant
modifier from OZ as stopping reentrancyIERC721
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!
The text was updated successfully, but these errors were encountered: