fix: propagate actual 403 reason from Google API#2272
Open
thebtf wants to merge 2 commits intolbjlaq:mainfrom
Open
fix: propagate actual 403 reason from Google API#2272thebtf wants to merge 2 commits intolbjlaq:mainfrom
thebtf wants to merge 2 commits intolbjlaq:mainfrom
Conversation
… message Previously, when quota fetch returned 403, the response body was discarded and a generic "quota fetch denied" string was stored as forbidden_reason. Now the actual API response body is read and propagated through QuotaData.forbidden_reason → mark_account_forbidden → frontend AccountErrorDialog, which already parses JSON error messages.
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.
Summary
Changes
quota.rs: Read response body on 403 and store inQuotaData.forbidden_reasonscheduler.rs: Useforbidden_reasonfrom quota data instead of hardcoded string (2 locations)claude.rs: Include first 500 chars of error body in proxy handler log messageTest plan