flywithu/CryptoExchange.Net
1
0
Fork 0
mirror of https://github.com/JKorf/CryptoExchange.Net synced 2026-02-16 14:13:46 +00:00
Code Issues Releases Wiki Activity

Allow the same websocket connection sequence number to be recorded multiple times

Browse Source
This commit is contained in:
Jkorf 2026-01-13 11:16:37 +01:00
parent 34ee2d3690
commit 669d1f7c9e
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
CryptoExchange.Net/Sockets/Default/SocketConnection.cs
View File

@ -1291,8 +1291,9 @@ namespace CryptoExchange.Net.Sockets.Default
public void UpdateSequenceNumber(long sequenceNumber) public void UpdateSequenceNumber(long sequenceNumber)
{ {
if (ApiClient.EnforceSequenceNumbers if (ApiClient.EnforceSequenceNumbers
&& _lastSequenceNumber != 0 && _lastSequenceNumber != 0 // Initial value is 0
&& _lastSequenceNumber + 1 != sequenceNumber) && _lastSequenceNumber != sequenceNumber // When there are multiple listeners for the same message it's possible this gets recorded multiple times, shouldn't be an issue
&& _lastSequenceNumber + 1 != sequenceNumber) // Expected value
{ {
// Not sequential // Not sequential
_logger.LogWarning("[Sckt {SocketId}] update not in sequence. Last recorded sequence number: {LastSequence}, update sequence number: {UpdateSequence}. Reconnecting", SocketId, _lastSequenceNumber, sequenceNumber); _logger.LogWarning("[Sckt {SocketId}] update not in sequence. Last recorded sequence number: {LastSequence}, update sequence number: {UpdateSequence}. Reconnecting", SocketId, _lastSequenceNumber, sequenceNumber);