-
Notifications
You must be signed in to change notification settings - Fork 98
Add a self-check test for processing a message which exceeds nanopb field size limits #589
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
Conversation
7f515e2 to
6a41ce1
Compare
andozw
left a comment
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.
Looks good to me. Just a couple of nits and mostly just questions for my own learning.
a990dd0 to
d1c3725
Compare
oreparaz
left a comment
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.
nice explanations 💯
92b5bfd to
68be7dd
Compare
oreparaz
left a comment
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.
Nice work, there's a conflict with core/CMakeLists.txt so happy to re stamp if needed.
68be7dd to
d7a10dc
Compare
d7a10dc to
fec311f
Compare
|
Squished all 4 commits together |
fec311f to
eae5fa4
Compare
See title. This verifies that nanopb refuses to parse such messages, rather than blowing the stack.