Repository navigation
fix(api): pace account refreshes and handle Cloudflare 403 challenges - #13
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Refreshing many ChatGPT accounts currently fans out up to ten simultaneous requests to the usage and account-metadata endpoints. This may trigger Cloudflare's 403 challenge and prevent status refreshes for multiple accounts.
Changes
Backport upstream PR Lampese#203 to the current fork:
Checks
git diff --checkpassed. Frontend, Rust and cross-platform checks are delegated to GitHub CI; this branch has not been deployed. The change affects refresh latency with many accounts, so retain the PR as draft until CI and behavior are reviewed.Adapted from Lampese#203.