Skip to content

[FEATURE] Add generalized support for throttling #383

Closed

Description

@jeffreyaven

Feature Description
Need a generalized framework and config definition(s) to deal with API rate limiting, catering for each providers implementation. The framework should allow for tuning of a backoff and retry strategy.

Activity

  1. Sneha41sb commented on Jul 19, 2026

    @Sneha41sb
    Contributor

    Hi @jeffreyaven, I would love to take this issue on! I'm planning to implement a generalized throttling and exponential backoff framework within the HTTP transport layer to handle transient rate-limiting status codes (like 429) across providers.

  2. jeffreyaven commented on Jul 19, 2026

    @jeffreyaven
    MemberAuthor

    assigned @Sneha41sb please supply a plan before you implement anything to implement this feature you would need to raise an issue in stackql/any-sdk which is the interface for stackql to providers, once implemented there with a tag pushed, the any-sdk version is vendored into the stackql core and wired through

  3. Sneha41sb commented on Aug 23, 2026

    @Sneha41sb
    Contributor

    Hi @jeffreyaven, thank you! Here is the proposed plan:

    1. stackql/any-sdk Implementation:

      • Define a generalized RateLimitConfig struct in the provider specification schema to capture backoff parameters (strategy, max retries, initial/max delay, status codes like 429/403).
      • Implement a reusable HTTP RoundTripper / transport middleware in any-sdk that handles exponential backoff, jitter, context.Context cancellation, and respects Retry-After headers.
      • Add unit tests covering status code interception and backoff timing.
    2. Core Integration (stackql/stackql):

      • Once the changes are merged and tagged in any-sdk, bump the vendored any-sdk dependency in stackql/stackql.
      • Wire the rate-limiting transport into the HTTP client setup where provider calls are dispatched.

    I will open the tracking issue in stackql/any-sdk right away.

  4. general-kroll-4-life commented on Aug 24, 2026

    @general-kroll-4-life
    Contributor

    @Sneha41sb another apology from me, this is resolved in #647

    Sorry for the inconvenience, closing now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions