Describe the bug
Sometimes after reconnecting after a connection drop, a ping request will be answered immediately by the response from the previous request which is waiting in the socket buffer. This creates a chain reaction where each request afterwards is answered by the response to the previous one, and so the ping latency is basically zero.
To Reproduce
Steps to reproduce the behavior:
- Run a ping test with a high count
- Mess with the connection to cause drops (can take a few tries)
Expected behavior
There should be a check that the sent sequence number = received sequence number.
Screenshots
Here, I added print statements in executor.py to display the sent/received sequence numbers
Desktop (please complete the following information):
Describe the bug
Sometimes after reconnecting after a connection drop, a ping request will be answered immediately by the response from the previous request which is waiting in the socket buffer. This creates a chain reaction where each request afterwards is answered by the response to the previous one, and so the ping latency is basically zero.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
There should be a check that the sent sequence number = received sequence number.
Screenshots
Here, I added print statements in executor.py to display the sent/received sequence numbers
Desktop (please complete the following information):