-
Notifications
You must be signed in to change notification settings - Fork 77
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
Issue #88 - Fix error: Message too long #89
base: master
Are you sure you want to change the base?
Conversation
…nd last chunks are marked with #0 as a delimiter
… so that client can assemble the chunks with more confidence
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.
This looks like great work!
It's a significant and complex new piece of functionality, so would you also be able to add a unit test to verify that this is working as expected? Something like /live/clip/add/notes
/ /live/clip/get/notes
, creating a large number of notes (exceeding the UDP size limit) and verifying that they are added successfully. I would then expect the unit test to fail before your fix, and pass after it. This could go in a new test file tests/test_api.py
.
Thanks again, this will be a great fix for operating on complex clips.
I've had a more detailed look at this, and have also added a unit test that can be used to test bidiretional long messages. It populates a clip with a large number of notes (~384), and then queries the notes to verify that they are all intact. It is easy to extend this to test a significantly larger number of notes by increasing the number of time shifts applied. It has shed light on a couple of limitations with this PR that need addressing:
Potentially (2) and (3) could become a separate Issue, but (1) should be fixed before this can be merged. @StrongBearCeo I realise it has been a while since this original PR - so if you're not still working on this, no worries, at some point I (or somebody else) will be able to get this across the line. |
@ideoforms that's great. I'll look into it when I have time, too. |
@StrongBearCeo have you had the time to look at it? :) |
@esaruoho I haven't. I've been using my own fork for this, actually |
Fix #88 , message too long will be split into smaller chunks