Skip to content

feat: implement rate limiting handling for Horizon 429 responses in E…#255

Open
Johnsource-hub wants to merge 1 commit intodetermined-001:mainfrom
Johnsource-hub:Client-side-rate-limiting-for-Horizon-429-responses
Open

feat: implement rate limiting handling for Horizon 429 responses in E…#255
Johnsource-hub wants to merge 1 commit intodetermined-001:mainfrom
Johnsource-hub:Client-side-rate-limiting-for-Horizon-429-responses

Conversation

@Johnsource-hub
Copy link
Copy Markdown

Closes #88

  • Add Horizon 429 rate-limit handling in EventEngine.ts
  • Honor Retry-After when present, otherwise wait at least 60000ms
  • Emit new watcher notification engine.rate_limited
  • Update index.ts and docs
  • Add tests for 429 with and without Retry-After

@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 28, 2026

@renoschubert is attempting to deploy a commit to the determined's projects Team on Vercel.

A member of the Team first needs to authorize it.

@drips-wave
Copy link
Copy Markdown

drips-wave Bot commented Apr 28, 2026

@Johnsource-hub Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

@determined-001
Copy link
Copy Markdown
Owner

Thanks for the contribution! Merging now.

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.28 — Client-side rate limiting for Horizon 429 responses

2 participants