Notifier.on_new_event has a new_token parameter.
To me, it looks like that's supposed to get the stream's new position passed (as you'd get from .get_current_token() on an ID generator).
In actuality, for some stream types (e.g. thread subscriptions), we are passing the stream_id from newly-inserted rows. In a multi-writer setup, new rows don't immediately become the current stream position.
It seems it only matters for a small handful of stream types, so the relatively-new streams getting this wrong might not have any real issues from this misunderstanding.
Notifier.on_new_eventhas anew_tokenparameter.To me, it looks like that's supposed to get the stream's new position passed (as you'd get from
.get_current_token()on an ID generator).In actuality, for some stream types (e.g. thread subscriptions), we are passing the
stream_idfrom newly-inserted rows. In a multi-writer setup, new rows don't immediately become the current stream position.It seems it only matters for a small handful of stream types, so the relatively-new streams getting this wrong might not have any real issues from this misunderstanding.