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.

Sign up for GitHub

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

Jump to bottom

Fuzz test CCF Codec #2377

Closed
fxamacker opened this issue Mar 10, 2023 · 3 comments
Closed

Fuzz test CCF Codec #2377

fxamacker opened this issue Mar 10, 2023 · 3 comments
Assignees
@SupunS
Labels
Feature Feedback

Comments

@fxamacker
Copy link
Member

Issue to be solved

The CCF codec (PR #2364) should be fuzz tested before deployment.

Suggested Solution

Fuzz testing the CCF codec should ideally be done by Cadence team with expertise in Cadence types and values.

It would be unusual for a brand new codec for a brand new data format to not have issues detected by fuzzing.
@fxamacker fxamacker mentioned this issue Mar 10, 2023
Closed
@j1010001 j1010001 assigned SupunS and unassigned turbolent Mar 13, 2023
@turbolent
Copy link
Member

@SupunS We could do something similar as we do for the existing fuzzer, or even extend it. Let's sync on it

@bluesign
Copy link
Contributor

is existing fuzzer public?

@turbolent
Copy link
Member

@bluesign No, the fuzzer is not public.

@SupunS SupunS closed this as completed Apr 5, 2023
@fxamacker fxamacker mentioned this issue Apr 18, 2023
Closed
24 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SupunS SupunS

Labels
Feature Feedback
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@turbolent @bluesign @SupunS @fxamacker