docs(mcp): fix stale 0.75s discovery-wait reference after #49208 - #49216
Closed
teknium1 wants to merge 1 commit into
Closed
docs(mcp): fix stale 0.75s discovery-wait reference after #49208#49216teknium1 wants to merge 1 commit into
teknium1 wants to merge 1 commit into
Conversation
…docstring The MCP discovery wait is now bounded by the config-driven mcp_discovery_timeout (default 1.5s), not the old 0.75s flat value. Updates the _schedule_mcp_late_refresh docstring that still cited ~0.75s after #49208 made the bound configurable.
Contributor
🔎 Lint report:
|
alt-glitch
added
type/docs
Contributor
Author
|
Merged via PR #49944 (docs salvage cluster 2). Your commit was cherry-picked onto current main with your authorship preserved in git log — rebase-merged so it lands under your name. Thanks for the contribution! |
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
2 participants
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
Corrects a stale docstring reference left after #49208 made the MCP discovery wait configurable. The
_schedule_mcp_late_refreshdocstring intui_gateway/server.pystill cited the old~0.75sflat bound; the wait is now bounded by the config-drivenmcp_discovery_timeout(default1.5s).Changes
tui_gateway/server.py: docstring~0.75s→bounded by the mcp_discovery_timeout config value, default 1.5s.Context
Follow-up to #49208. The original #49160 description also narrated a
5.0sdefault that never matched the shipped code (1.5s); that text lived only in the (now-closed) PR description, not in the repo, so there's nothing else to correct in-tree. This was the one stale value that actually landed in code.Docs-only; no behavior change.
Infographic