Skip to content

Bound implicit OAuth initialization waits - #104

Open
chubes4 wants to merge 1 commit into
trunkfrom
fix-103-oauth-initialize-timeout
Open

Bound implicit OAuth initialization waits#104
chubes4 wants to merge 1 commit into
trunkfrom
fix-103-oauth-initialize-timeout

Conversation

@chubes4

@chubes4 chubes4 commented Jul 29, 2026

Copy link
Copy Markdown

Summary

  • Bound implicit OAuth callback waits to the configured OAuth operation timeout instead of the five-minute coordination lock lifetime.
  • Bound secondary-process lock polling to the same operation budget without extending the deadline by a final one-second poll.
  • Add OAUTH_TIMEOUT_MS configuration for deterministic runtime and regression coverage.
  • Verify that headless MCP initialization returns the structured degraded response when no OAuth callback arrives, while successful callbacks still complete normally.

Closes #103.

Verification

  • npm run check
  • npm run build
  • npm test -- --runInBand (229 tests passed)
  • npx jest tests/unit/implicit-oauth-timeouts.test.ts tests/integration/dead-backend.test.ts --runInBand --detectOpenHandles

AI Assistance

OpenAI GPT-5.6 Terra through OpenCode drafted the implementation and regression tests. OpenAI GPT-5.6 Sol through OpenCode reviewed the change, corrected child-process teardown, and ran verification. Chris Huber reviewed and owns the submitted change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Implicit OAuth can block MCP initialize for the five-minute lock lifetime

1 participant