fix(bybit): normalize L2_BOOK callback timestamp using timestamp_norm… #1083
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bmoscon
approved these changes
May 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
The L2_BOOK callback for the Bybit exchange was using a raw integer conversion (
int(msg['ts'])) for the timestamp. This could lead to inconsistent units (seconds vs milliseconds) in backend processing.What Changed
timestampargument passed toself.book_callbackto useself.timestamp_normalize(int(msg['ts']))instead of the raw integer value.timestamp_normalize, we now correctly handle both seconds- and milliseconds-based inputs.