Comment 3 for bug 1917540

This is some debugging info I used. This following set of messages is normal when there is no problems.

NORMAL MESSAGES
Sending 4 messages
Received 2 messages
********************
Server Sequence: 8
Next Expected S: 32
Client Sequence: 28
Pending Offset: 5
Number Messages: 4
********************
Server Sequence: 10
Next Expected S: 32
Client Sequence: 32
Pending Offset: 4
Number Messages: 0

Then this is when there is the sequence jump, when using the fix in the pull request linked above.

SEQUENCE JUMP
Sending 6 messages
Received 0 messages
********************
Server Sequence: 20
Next Expected S: 200
Client Sequence: 64
Pending Offset: 5
Number Messages: 6
********************
Server Sequence: 20
Next Expected S: 200
Client Sequence: 200
Pending Offset: 0
Number Messages: 7

The sequence jump starts a resync and resetting the offsets, and things go back to normal, as in the following.

SEQUENCE JUMP AFTER RESYNC
Sending 24 messages
Received 2 messages
********************
Server Sequence: 20
Next Expected S: 224
Client Sequence: 200
Pending Offset: 0
Number Messages: 24
********************
Server Sequence: 22
Next Expected S: 224
Client Sequence: 224
Pending Offset: 24
Number Messages: 0