Repository navigation
Sign a pinned bot in after the MCP handshake - #294
Merged
Merged
Conversation
A seat with a bot name signed in before it answered the MCP handshake. A realm that was down or slow at boot made the host time the server out, and the host caches that failure for the rest of its session. The sign-in now runs after the handshake and retries a realm it cannot reach for as long as the seat runs. Default subscriptions, the COMMY_SUBSCRIBE seed, catch-up and the event pump follow once it signs in. A rejected sign-in still ends the server with its diagnostic. The editing-setting probe still runs before the handshake. It now gives up after five seconds and offers edit_message, as it already did on any other failure.
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 seat with a bot name signed in before it answered the MCP handshake. A realm that was down or slow at boot made the host time the server out, and the host caches that failure for the rest of its session. The sign-in now runs after the handshake and retries a realm it cannot reach for as long as the seat runs. Default subscriptions, the COMMY_SUBSCRIBE seed, catch-up and the event pump follow once it signs in. A rejected sign-in still ends the server with its diagnostic.
The editing-setting probe still runs before the handshake. It now gives up after five seconds and offers edit_message, as it already did on any other failure.