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
When connecting to PDS's firehose with a previous cursor, it occasionally skips a few sequential cursor values without emitting #info message.
To Reproduce
Steps to reproduce the behavior:
Connect to wss://agaric.us-west.host.bsky.network/xrpc/com.atproto.sync.subscribeRepos?cursor=13892059 sometime within the next hour
Read seq field from the first received message
Expected behavior
13892060
Actual behavior
13892061
Additional context
Yes, I know that the spec does not say they have to be sequential. But they are in the current implementation, and I'm checking the increment to detect a reset when connecting to Relay's firehose, which does not emit #info at all, so there's no other way to know if there's a break in continuity.
The text was updated successfully, but these errors were encountered:
Describe the bug
When connecting to PDS's firehose with a previous cursor, it occasionally skips a few sequential cursor values without emitting
#info
message.To Reproduce
Steps to reproduce the behavior:
wss://agaric.us-west.host.bsky.network/xrpc/com.atproto.sync.subscribeRepos?cursor=13892059
sometime within the next hourseq
field from the first received messageExpected behavior
13892060
Actual behavior
13892061
Additional context
Yes, I know that the spec does not say they have to be sequential. But they are in the current implementation, and I'm checking the increment to detect a reset when connecting to Relay's firehose, which does not emit
#info
at all, so there's no other way to know if there's a break in continuity.The text was updated successfully, but these errors were encountered: