8000 (fix) improve handling of unhealthy websockets connections (backport #2854) by mergify[bot] · Pull Request #2873 · dydxprotocol/v4-chain · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

(fix) improve handling of unhealthy websockets connections (backport #2854) #2873

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.

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

Conversation

mergify[bot]
Copy link
Contributor
@mergify mergify bot commented Jun 3, 2025

Changelist

Publishing errors were caught on each attempt to send a message from a batch to a subscriber. Now, first error in publishing to a subscriber will break the publishing loop, minimizing redundant error generation.

Websockets that failed to respond to pings were terminated and cleaned up without an attempt to close the connection with an informative error.

remove unnecessary typed buffer conversions

minimize connection lookups by passing Connection and not id

add connectionId to Connection

extract metrics to methods for clarity

simplify error handling in wss send

add constants for websocket error codes

remove ad-hoc listener removal in InvalidMessageHandler

Test Plan

Unit Tests

Run in internal environments and public testnet

Summary by CodeRabbit

  • Bug Fixes
    • Improved error handling for message sending, including better tracking and suppression of expected connection errors.
  • Chores
    • Cleaned up unnecessary debug logging and improved error propagation during message forwarding for more robust error reporting.
    • Simplified message encoding and decoding by removing redundant data conversions across multiple services for improved efficiency.
    • Enhanced WebSocket connection management with consistent use of connection objects and added heartbeat timeout handling.
    • Updated tests for WebSocket service to improve clarity and precision in connection lifecycle verification.
  • New Features
    • Added new WebSocket close codes for going away and heartbeat timeout scenarios.
    • Introduced a standardized rate-limited close message constant for WebSocket connections.

This is an automatic backport of pull request #2854 done by [Mergify](https://mergify.com).

Before, publishing errors were caught on each attempt to send a message from a batch to a subscriber.
Now, encountering an error in publishing will stop publishing to that subscriber, minimizing redundant error generation.

Before, when a websocket client would fail to respond to pings, it was disconnected by termination and cleanup.
Now, the websocket is closed with an error appropriate for heartbeat timeout.
In the event the websocket is healthy but the subscriber is not responding to pings, they will receive the informative error.

Remove unnecessary typed buffer conversions.

Minimize connection lookups by passing Connection and not ConnectionId.

Add connectionId to `Connection` for use in logging and error generation.

Extract metrics to methods for clarity in critical code segments.

Simplify error handling in wss send.

Add constants for websocket error codes.

Remove ad-hoc listener removal in InvalidMessageHandler.

(cherry picked from commit e9d1551)
Copy link
Contributor
coderabbitai bot commented Jun 3, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@UnbornAztecKing UnbornAztecKing merged commit fb5bba2 into release/indexer/v8.x Jun 3, 2025
17 checks passed
@UnbornAztecKing UnbornAztecKing deleted the mergify/bp/release/indexer/v8.x/pr-2854 branch June 3, 2025 17:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

1 participant
0