-
Notifications
You must be signed in to change notification settings - Fork 21
parse_ipc_message should return exception instead of return None if parse failed #97
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
… message length or bad continuation marker
… message length or bad continuation marker
|
@luoyuxia Would appreciate a review here |
luoyuxia
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.
@leekeiabstraction Thanks for your pr. Left minor comments. PTAL
…ue to unexpected message length or bad continuation marker
…ue to unexpected message length or bad continuation marker
|
Thanks @luoyuxia , pushed new changes based on your recommendations. I've attempted running Integ test but couldn't. Might need to sync with you on how to do that. |
luoyuxia
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.
@leekeiabstraction Thanks for the pr. LGTM.
I append a small commit to fix ci. Merging....
Btw, you can run
cargo fmt
cargo clippy --all-targets --fix --allow-dirty --allow-staged
to make ci happy
Purpose
Linked issue: close #72
#72