Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
betegon
force-pushed
the
fix/mcp-project-verification
branch
from
October 20, 2026 16:01
f7a69f0 to
d02b400
Compare
This branch was previously deployed
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.
Project-scoped OAuth requests can spend five seconds verifying project capabilities before continuing with unknown capabilities. The project response also serializes organization metadata that this preflight does not use; production traces showed that work waiting on an auth-config RPC.
Request
collapse=organizationonly for this preflight, preserving the shared client's default response and all four capabilities. Cache timeout fallbacks for 60 seconds and register writes withwaitUntil. Timeout entries use separate keys, and verified entries are read first, so a late concurrent timeout cannot overwrite known capabilities or shorten their 15-minute TTL. Project verification failures with HTTP 401/403/404 remain uncached.This supersedes the 60-second project-timeout cache and
waitUntilcache-write scheduling proposed in #1035. Its v2 cache format, Zod validation, slug validation, and reuse of organization cache entries during project verification remain outside this PR.Verification
pnpm run tscandpnpm run lintpassed. Fullpnpm run testpassed on Linux x64 (14,049 tests; 51 existing skips).nullafter an overlapping request times out. It passes afterward, retaining verified capabilities even after the timeout entry expires, without another API request.ExecutionContextand consumes the MCP response while KV is blocked. Controlled mutations removingwaitUntil, passing it unbound, and sharing the timeout/verified key each fail the corresponding regression test. Production code was restored before the full gate.collapse=organization.The API timings are not full MCP latency, and no benchmark request reproduced a five-second spike. Production timeout-rate reduction remains unverified. KV propagation and requests already in flight can still temporarily return unknown capabilities; separate keys prevent destructive overwrites, not propagation delays.