Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Debug CometWsClient delivery order #13

Open
ashayp22 opened this issue Aug 3, 2024 · 0 comments
Open

Debug CometWsClient delivery order #13

ashayp22 opened this issue Aug 3, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@ashayp22
Copy link
Contributor

ashayp22 commented Aug 3, 2024

Screenshot 2024-08-01 at 10 41 59 AM

A bug on Aug 1, 2024 was discovered where the WebSocket client (CometWsClient) added a block height n+1 to the event queue before an earlier block height n. This caused the indexer to process the later block height before the earlier block height. An immediate fix was throwing an error before this happened, but we need to look into why the WebSocket client did this since the queue add() logic isn't asynchronous and WebSocket delivers messages in FIFO order.
@ashayp22 ashayp22 added the bug Something isn't working label Aug 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ashayp22