fix: recognised Cyber access denials - #210
Merged
Merged
Conversation
- Matched exact forbidden access messages when upstream omitted structured details. - Retried eligible accounts across HTTP and WebSocket paths without marking quota exhausted.
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
1 participant
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.
A Cyber request can receive
403 Forbiddenwith only “The requested Cyber access program is not authorized for this workspace.” Earlier routing recognised structuredcodeandparamfields, so this response reached Codex instead of triggering account failover. CQ now recognises that exact message at status 403 across HTTP and WebSocket, keeps unrelated 403s unchanged, and does not mark quota exhausted.Targeted race tests reproduce both leaked paths before the fix and pass afterward.
go build ./...,go vet ./..., andgo test -race -count=1 ./...passed.