-
Notifications
You must be signed in to change notification settings - Fork 18
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
Fixing #40: Support KeyValue #43
base: master
Are you sure you want to change the base?
Conversation
Merge pajowu/master
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. Howevery I want to keep the frame counting thing, because that might be the only mechanism we have to find new frames without weird crashes. I wrote a bit on that in the inline comment, I hope that makes sense?
Dear @pajowu , Thanks for your feedback. Please see my reply in the inline comment. |
Sorry for the long wait, I added another comment to our inline discussion |
Thanks for your reply. If CI does not throw any error, it's ready to be merged from my side. |
I'm sorry that the commit history got so messy ... |
Hello,
This PR is intended to fix #40 by adding support for the output of keyvalue frames. In addition, there are some small code cleanups. For example: I have removed checking the number of frames in
frame.rs::new
. I think there is no case in protobuf where a frame has two different contents and it is only necessary to check for unknown frame contents.Best,
mutlusun