-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
fix: out of range in MustUnmarshal #7485
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Could you add a test case and perhaps a link to the report?
done |
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please also fix the lint check
Signed-off-by: AdamKorcz <adam@adalogics.com>
@AdamKorcz Is there a link to the new report that reflects this fix? |
Thanks. The OSS-fuzz issue should resolve automatically during the next build which will most likely be sometime within 24 hours. |
Sounds good. Thanks! |
Signed-off-by: AdamKorcz <adam@adalogics.com>
This adds a more readable and easier recoverable message for the case when the input is of length 0.
This was reported by OSS-fuzz (issue 43202).