Skip to content

fix: stop filtering NewMarket/MarketResolved WS events by subscribed assets#16

Open
yovanoc wants to merge 1 commit intoPolymarket:mainfrom
yovanoc:fix/ws-newmarket-marketresolved-filtering
Open

fix: stop filtering NewMarket/MarketResolved WS events by subscribed assets#16
yovanoc wants to merge 1 commit intoPolymarket:mainfrom
yovanoc:fix/ws-newmarket-marketresolved-filtering

Conversation

@yovanoc
Copy link
Copy Markdown

@yovanoc yovanoc commented Apr 26, 2026

NewMarket and MarketResolved are broadcast events with new/different asset IDs that will never match the subscriber's asset_ids_set, causing them to be silently dropped. These events should always be yielded to consumers.


Note

Low Risk
Low risk: small change limited to WebSocket message filtering, but it can increase the volume of market-channel events delivered to subscribers.

Overview
Stops filtering WsMessage::NewMarket and WsMessage::MarketResolved by the subscriber’s asset_ids_set in subscription.rs; these event types are now always yielded to market subscribers so they aren’t silently dropped when they reference new/different asset IDs.

Reviewed by Cursor Bugbot for commit 9905d4b. Bugbot is set up for automated code reviews on this repo. Configure here.

…assets

NewMarket and MarketResolved are broadcast events with new/different asset IDs
that will never match the subscriber's asset_ids_set, causing them to be
silently dropped. These events should always be yielded to consumers.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant