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
{{ message }}
This repository has been archived by the owner on Apr 16, 2022. It is now read-only.
It seems to me like heartbeats don't work when default-features = false and the feature "use-webrtc" is enabled.
If I toggle back to not using WebRTC then I see them arrive between both client and server, and when I toggle WebRTC back on for both client/server then they don't manage to receive them.
I have added prints in my local fork to verify what is happening and the net.send(handle, Packet::new()).unwrap(); line that sends the heartbeats is reached. However, the receiving routine in Ok(packet) => { ... packet read here... in receive_packets is never triggered on the opposite end. This is seen accordingly on both client and server.
Could this be due to how the heartbeats are not turbulence messages and pure UDP (as per the heartbeats readme file)
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It seems to me like heartbeats don't work when default-features = false and the feature "use-webrtc" is enabled.
If I toggle back to not using WebRTC then I see them arrive between both client and server, and when I toggle WebRTC back on for both client/server then they don't manage to receive them.
I have added prints in my local fork to verify what is happening and the
net.send(handle, Packet::new()).unwrap();
line that sends the heartbeats is reached. However, the receiving routine inOk(packet) => { ... packet read here...
inreceive_packets
is never triggered on the opposite end. This is seen accordingly on both client and server.Could this be due to how the heartbeats are not turbulence messages and pure UDP (as per the heartbeats readme file)
The text was updated successfully, but these errors were encountered: