Repository navigation
Wait for fresh provider readiness before refusing completions - #25
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.
Chat Completions could refuse queued work using a startup authentication failure while the scheduler was still checking the selected worker. Wait for a newer readiness revision before returning
execution_unavailable; buffered and streaming completion requests can finish when the fresh check succeeds. A fresh unavailable result still returns HTTP 503 without executing a worker.Prepare version 0.2.17 with matching CLI, HTTP, MCP, Claude/Codex plugin and marketplace metadata, updated installation/readiness guidance, and 138 current controlled console screenshots.
Pin the development-only Vite dependency to 8.3.3 for the three upstream editor-launch security advisories. The lockfile audit reports no remaining vulnerabilities.
Validation:
Screenshots and worker readiness cases use controlled fixtures. This change does not upgrade the active local bridge or establish fresh subscription/model acceptance. Linux and Windows packages remain subject to the PR's native CI matrix.