You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE] Add generalized support for throttling #383
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.
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.
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
Hi @jeffreyaven, thank you! Here is the proposed plan:
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.
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.
Activity
Sneha41sb commentedon Jul 19, 2026
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.
jeffreyaven commentedon Jul 19, 2026
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-sdkversion is vendored into thestackqlcore and wired throughSneha41sb commentedon Aug 23, 2026
Hi @jeffreyaven, thank you! Here is the proposed plan:
stackql/any-sdkImplementation:RateLimitConfigstruct in the provider specification schema to capture backoff parameters (strategy, max retries, initial/max delay, status codes like 429/403).RoundTripper/ transport middleware inany-sdkthat handles exponential backoff, jitter,context.Contextcancellation, and respectsRetry-Afterheaders.Core Integration (
stackql/stackql):any-sdk, bump the vendoredany-sdkdependency instackql/stackql.I will open the tracking issue in
stackql/any-sdkright away.general-kroll-4-life commentedon Aug 24, 2026
@Sneha41sb another apology from me, this is resolved in #647
Sorry for the inconvenience, closing now