fix: repair pool credential handling and connection selection - #1732
Merged
Merged
Conversation
📊 Code coverage
Gate: line coverage must stay at or above the threshold. Ratchet plan (W21): Backend → 55%, CLI → 50%, Frontend → 30% by quarter end. |
14 of 15 tasks
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
Bad request: API key is failedwhen one connection has an unusable stored credential. Report that connection as unavailable and let priority pools dispatch to a healthy backup, while preserving direct-proxy HTTP 400 responses and genuine database errors.Follow-up to #1731. Related to #1680.
Test Plan
8d6a5a50): CI Pipeline, all CodeQL jobs, frontend and backend coverage passed. Backend CI ran 7,140 passing tests (5 skipped by the suite). Squash-merged intomainas89257aa5.Checklist