[Bug]: not able to stream due to lost packages at end of last stream

Client version

latest

Node version

all

Operating System type

Other

Operating system version

all

Describe the bug

If packets are lost at the end of a stream the client cannot keep track of the correct sequence number. Therefore any attempt at streaming after that will fail, since the client always expects a sequence number which will ‘never’ be reached (until the sequence numbers were reset and it all starts again at zero).

You can see this in the log with the sequence number 37040 which was lost right when the stream was closed. It only is received after the stream is already closed and then it is ignored. The next stream attempt fails, since the client waits on this sequence number.

To reproduce

1. Go to ‘…’
2. Click on ‘…’
3. Scroll down to ‘…’
4. See error

Screenshots & Logfiles

squence_number_loss.log

Additional context

No response

[thieren]

After testing a few days I would say this works now as expected. At least I didn’t experience any stream related hiccups anymore since I improved the network performance.

I am curious though if there is something that can be done about the errors I’ve encountered, since I properly won’t be the only user with bad connection issues. And to some it might not be that obvious that this is a network issue on their side and not directly related to this client.

[thieren]

Thx!

Will test with new version and see if it happens again.

Seems like I’ll have to look into my network performance with all those lost packets, but at least it helped finding a few minor bugs. 😃