Skip to content

chore(controller): spread out API sync requests#939

Draft
basti1302 wants to merge 1 commit into
mainfrom
ope-248-spread-api-sync-requests-to-avoid-hitting-rate-limits-and
Draft

chore(controller): spread out API sync requests#939
basti1302 wants to merge 1 commit into
mainfrom
ope-248-spread-api-sync-requests-to-avoid-hitting-rate-limits-and

Conversation

@basti1302
Copy link
Copy Markdown
Member

Rate-limit API sync requests on the client side to avoid hitting the backend's rate limit.

@basti1302 basti1302 force-pushed the ope-248-spread-api-sync-requests-to-avoid-hitting-rate-limits-and branch 3 times, most recently from e0a60cc to 9a266c5 Compare April 13, 2026 09:52
Rate-limit API sync requests on the client side to avoid hitting the
backend's rate limit.
@basti1302 basti1302 force-pushed the ope-248-spread-api-sync-requests-to-avoid-hitting-rate-limits-and branch from 9a266c5 to 0f3984f Compare April 13, 2026 10:33
@sonarqubecloud
Copy link
Copy Markdown

@basti1302
Copy link
Copy Markdown
Member Author

It is somewhat questionable if we actually want to add this. We should either proceed with this PR or cancel OPE-248.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant