-
-
Notifications
You must be signed in to change notification settings - Fork 451
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 ped sync behavior #3965
Fix ped sync behavior #3965
Conversation
cc @tederis |
This is potentially backwards incompatible. But due to the bit flags overlapping it may be hard to distinguish whether it pre-PR or post-PR behaviour. I think this could be merged without noticable issues. See the explanation in Discord: https://discord.com/channels/801330706252038164/801411628600000522/1330055415760818208 |
Could we get more maintainers' opinions on this? |
We could also just ignore the issue and live with the overlap and simply get rid of the BitStream-versioned blocks with the next version bump |
Okay, let's close this then? |
Fine by me. |
The problem with it is that without this PR the ped syncronization becomes unstable which potentially can (but depends on internal BitStream implementation) lead to crashes. |
Fixes unexpected ped sync behavior after #3936