-
Notifications
You must be signed in to change notification settings - Fork 919
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
blob: (*Blob).UnmarshalJSON crashes with simple JSON []byte("{}") #3727
Comments
odeke-em
added a commit
to orijtech/celestia-node
that referenced
this issue
Sep 16, 2024
This changes adds fuzzers+corpra that found some bugs, along with tests and reproducers to catch future regressions. Fixes celestiaorg#3727 Fixes celestiaorg#3728 Fixes celestiaorg#3729 Fixes celestiaorg#3730 Fixes celestiaorg#3731
I have mailed out a PR with the fixes along with the fuzzers per #3732 |
odeke-em
added a commit
to orijtech/celestia-node
that referenced
this issue
Sep 16, 2024
This changes adds fuzzers+corpra that found some bugs, along with tests and reproducers to catch future regressions. Fixes celestiaorg#3727 Fixes celestiaorg#3728 Fixes celestiaorg#3729 Fixes celestiaorg#3730 Fixes celestiaorg#3731
odeke-em
added a commit
to orijtech/celestia-node
that referenced
this issue
Sep 16, 2024
This changes adds fuzzers+corpra that found some bugs, along with tests and reproducers to catch future regressions. Fixes celestiaorg#3727 Fixes celestiaorg#3728 Fixes celestiaorg#3729 Fixes celestiaorg#3730 Fixes celestiaorg#3731
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Celestia Node version
1a1286f
OS
darwin
Install tools
No response
Others
No response
Steps to reproduce it
If you run this very simple repro
Expected result
No panic
Actual result
Relevant log output
No response
Is the node "stuck"? Has it stopped syncing?
No response
Notes
To fix it, please check that the namespace is non-empty
The text was updated successfully, but these errors were encountered: