Repository navigation
Expose safe bridge diagnostics for blocked runner startup - #34
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.
Runner startup is blocked in production with
Bridge refused operation (409), which hides both the failed operation and the bridge's conflict reason. Include the HTTP method and operation path, forward only recognized fixed bridge diagnostics, and log the same safe message in the runner Worker.A runner RPC regression test verifies that a known conflict reaches the caller and arbitrary response text containing credential-like fixture values does not. The test failed before the change and passes afterward. Runner typechecking and
vp checkpass; the full runner suite is still running.This is a diagnostic change, not a fix for the production startup failure. Deploying it will let the next failed attempt distinguish a clone reconciliation problem from a generation or epoch conflict. It does not reset the existing session or workspace.