Skip to content

Group polymarket subscriptions by configurable delay #2271

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

Merged
merged 1 commit into from
Jan 30, 2025

Conversation

ryantam626
Copy link
Contributor

Pull Request

Allow user to configure the delay of non-initial Polymarket WS connection per #2238

This is to avoid overwhelming polymarket by establishing many WS at once, since polymarket will throw 429 at us.

We separate out the initial delay and the non-initial delay just in case users wanting more fine-grained control about the delay.

N.B. ws_connection_delay_secs has a new meaning now - this is no longer the config for the initial delay but for non-intiial WS connection delay - this might need to be communicated to end users.

Type of change

  • New feature (non-breaking change which adds functionality)

How has this change been tested?

Built and ran locally against polymarket.

This is to avoid overwhelming polymarket by establishing many WS at
once, since polymarket will throw 429 at us.

We separate out the initial delay and the non-initial delay just in case
users wanting more fine-grained control about the delay.
@cjdsellers cjdsellers changed the title feat: Group polymarket subscriptions by configurable delay Group polymarket subscriptions by configurable delay Jan 30, 2025
@cjdsellers
Copy link
Member

Hi @ryantam626

Great work, and thanks for the contribution 🙏

I'll make sure to communicate the config meaning change in the release notes.

@cjdsellers cjdsellers merged commit 9420722 into nautechsystems:develop Jan 30, 2025
13 checks passed
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.

2 participants