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.

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

Full Node Streaming Order Filtering by Subaccount impl and tests #2693

Conversation

UnbornAztecKing
Copy link

@UnbornAztecKing UnbornAztecKing commented Jan 17, 2025

Changelist

Full Node Streaming provides an initial state and streaming updates for positions, orders, prices and fills.

The subscription API admits an optional sub account ID filter, which is only applied to the initial positions and position changes.

The user would like to apply the sub account ID filter to the order messages, in addition to position messages.

The change will add boolean flags to the Websocket and GRPC streaming API's:

  • filterOrdersBySubaccountId boolean field for WS request (if not provided, default to False)
  • filter_orders_by_subaccount_id boolean field for StreamOrderbookUpdatesRequest protobuf (if not provided, default to False)

For all endpoints, the previous behavior of not filtering orders for subaccounts is preserved by default.

If filtering orders is not specified, the code path remains the same for looping over stream updates.
If filtering orders is specified, each slice of updates received from the subscription updatesChannel will be filtered like:

  • if the message is not a StreamUpdate_OrderbookUpdate, forward it
  • if the message is a StreamUpdate_OrderbookUpdate, forward it only if one of the OffChainUpdateV1 messages inside are for a target subaccount

Test Plan

Unit test

Author/Reviewer Checklist

  • If this PR has changes that result in a different app state given the same prior state and transaction list, manually add the state-breaking label.
  • If the PR has breaking postgres changes to the indexer add the indexer-postgres-breaking label.
  • If this PR isn't state-breaking but has changes that modify behavior in PrepareProposal or ProcessProposal, manually add the label proposal-breaking.
  • If this PR is one of many that implement a specific feature, manually label them all feature:[feature-name].
  • If you wish to for mergify-bot to automatically create a PR to backport your change to a release branch, manually add the label backport/[branch-name].
  • Manually add any of the following labels: refactor, chore, bug.

Summary by CodeRabbit

Summary by CodeRabbit

  • New Features

    • Added an option to filter order updates during streaming.
    • Enhanced orderbook subscription with optional order filtering capability.
    • Introduced a new parameter for filtering orders in WebSocket server requests.
  • Improvements

    • Updated streaming interfaces to support the new filtering mechanism.
    • Enhanced error handling for parsing new parameters.
  • Technical Updates

    • Modified protocol buffers and SDK types to include filterOrders parameter.
    • Updated WebSocket server to parse new query parameter.
    • Added test coverage for new streaming functionality.
    • Enhanced functionality to extract subaccount IDs from off-chain updates.
    • Introduced a method to retrieve subaccount IDs from various update messages.

@UnbornAztecKing UnbornAztecKing requested a review from a team as a code owner January 17, 2025 21:34
Copy link
Contributor

coderabbitai bot commented Jan 17, 2025

Warning

Rate limit exceeded

@github-actions[bot] has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 19 minutes and 21 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 56cc48e and c5dda04.

⛔ Files ignored due to path filters (1)
  • protocol/x/clob/types/query.pb.go is excluded by !**/*.pb.go
📒 Files selected for processing (10)
  • indexer/packages/v4-protos/src/codegen/dydxprotocol/clob/query.ts (6 hunks)
  • proto/dydxprotocol/clob/query.proto (1 hunks)
  • protocol/streaming/full_node_streaming_manager.go (6 hunks)
  • protocol/streaming/full_node_streaming_manager_test.go (1 hunks)
  • protocol/streaming/noop_streaming_manager.go (1 hunks)
  • protocol/streaming/types/interface.go (1 hunks)
  • protocol/streaming/util/util.go (1 hunks)
  • protocol/streaming/util/util_test.go (1 hunks)
  • protocol/streaming/ws/websocket_server.go (3 hunks)
  • protocol/x/clob/keeper/grpc_stream_orderbook.go (1 hunks)

Walkthrough

This pull request introduces a new feature to filter orderbook updates based on specific subaccount IDs across multiple components of the dYdX protocol. The changes span from proto definitions to streaming managers, adding a boolean flag filterOrdersBySubaccountId that allows more granular control over which order updates are received. The modification enables clients to request orderbook updates that only include orders associated with specified subaccount IDs, enhancing the flexibility of the streaming mechanism.

Changes

File Change Summary
indexer/packages/v4-protos/src/codegen/dydxprotocol/clob/query.ts Added filterOrdersBySubaccountId boolean property to StreamOrderbookUpdatesRequest and StreamOrderbookUpdatesRequestSDKType interfaces.
proto/dydxprotocol/clob/query.proto Added filter_orders_by_subaccount_id field to StreamOrderbookUpdatesRequest message.
protocol/streaming/full_node_streaming_manager.go Added methods for creating and managing orderbook subscriptions with subaccount filtering, modified Subscribe method to include filterOrdersBySubAccountId.
protocol/streaming/types/interface.go Updated Subscribe method signature to include filterOrders parameter.
protocol/streaming/ws/websocket_server.go Added parseFilterOrders function to handle new query parameter.
protocol/x/clob/keeper/grpc_stream_orderbook.go Modified StreamOrderbookUpdates to pass filter parameter to Subscribe.
protocol/streaming/full_node_streaming_manager_test.go Introduced tests for filtering stream updates based on subaccount IDs.
protocol/streaming/util/util.go Added GetOffChainUpdateV1SubaccountIdNumber function to extract subaccount ID from updates.
protocol/streaming/util/util_test.go Added tests for GetOffChainUpdateV1SubaccountIdNumber function.
protocol/streaming/noop_streaming_manager.go Updated Subscribe method signature to include an additional boolean parameter.

Possibly related PRs

Suggested Labels

refactor, backport/protocol/v5.1.x

Suggested Reviewers

  • jonfung-dydx
  • roy-dydx

Poem

🐰 Hop, hop, filtering streams so bright,
Subaccount orders now in clear sight!
Boolean flag waves its magic wand,
Streaming updates now more fond
Of precision's gentle might! 🌟


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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 docstrings to generate docstrings for this PR. (Beta)
  • @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 deleted the mattweeks/filtered-order-stream-specific-subaccounts-squash branch January 17, 2025 21:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

1 participant