You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our integration test failed because on one node all peers had been disconnected due to "Short buffer to be filled" error. The read buffer capacity is set here. Error means that somewhere (?) we're sending/reading messages more than 16kB, which should not be possible if all nodes are using the same webrtc FRAMED transport.
We are behind on the webrtc-rs updates because thus far, we were been blocked on webrtc-rs/webrtc#413 not being fixed. But the next release should fix this and we can upgrade, I think.
Summary
Our integration test failed because on one node all peers had been disconnected due to "Short buffer to be filled" error. The read buffer capacity is set here. Error means that somewhere (?) we're sending/reading messages more than 16kB, which should not be possible if all nodes are using the same webrtc FRAMED transport.
Refs paritytech/substrate#12529 (comment)
Expected behaviour
Expect nodes sending messages to respect the read buffer capacity.
Actual behaviour
Possible Solution
webrtc-rs/webrtc#273 although that requires more thinking... plus I think we want to switch to
str0m
#3659Version
Would you like to work on fixing this bug?
Yes
The text was updated successfully, but these errors were encountered: