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

[ 💻 Clarity VM ] General fuzz testing #5

Closed
obycode opened this issue Aug 4, 2023 · 4 comments
Closed

[ 💻 Clarity VM ] General fuzz testing #5

obycode opened this issue Aug 4, 2023 · 4 comments

Comments

@obycode
Copy link
Collaborator

obycode commented Aug 4, 2023

The clar2wasm library needs to handle any random Clarity coming in from users (although it has passed through the parser and analysis passes before reaching here). It should be hardened to handle whatever comes in, handling errors gracefully.

@will-corcoran will-corcoran changed the title General fuzz testing [ 💻 Clarity VM ] General fuzz testing Aug 5, 2023
@obycode obycode added L labels Aug 8, 2023
@obycode obycode removed their assignment Sep 20, 2023
@smcclellan smcclellan added this to the WASM Phase 1 milestone Mar 12, 2024
@smcclellan
Copy link
Collaborator

@moodmosaic Would you be able to work on this one, or add input on the approach?

@moodmosaic
Copy link
Member

Thanks @smcclellan, we have been doing this for a while, finding issues and fixing them. Some of the issues we found are

and a few others that I can't remember off the top of my head. /cc @obycode

@smcclellan
Copy link
Collaborator

@moodmosaic Can this issue be closed then, if fuzz testing is already in place & helping to find issues? Or is there an improvement that this ticket could track?

@moodmosaic
Copy link
Member

@smcclellan, yes, this issue can be closed.

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

No branches or pull requests

3 participants