Skip to content

Fix: dev-proxy timeout configuration - #487

Merged
debugmcpdev merged 2 commits into
debugmcp:mainfrom
abhijeetnardele24-hash:fix/issue-472-dev-proxy-timeout-v2
Aug 25, 2026
Merged

Fix: dev-proxy timeout configuration#487
debugmcpdev merged 2 commits into
debugmcp:mainfrom
abhijeetnardele24-hash:fix/issue-472-dev-proxy-timeout-v2

Conversation

@abhijeetnardele24-hash

Copy link
Copy Markdown
Contributor

Closes #472 (Replacing #474 with a clean, unstacked branch). Adds DEV_PROXY_BUILD_TIMEOUT_MS and correctly intercepts SIGTERM/timeouts so they are distinct from actual build failures.

@codecov

codecov Bot commented Aug 25, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@debugmcpdev

Copy link
Copy Markdown
Collaborator

Merging — thanks for the clean v2, and for validating the env var input (non-finite/negative falls back to the default, nice touch). One non-blocking follow-up idea: naming DEV_PROXY_BUILD_TIMEOUT_MS in the timeout message itself would tell the reader which knob to raise without opening the docs. Credited in the CHANGELOG under [Unreleased].

@debugmcpdev
debugmcpdev merged commit 4adc61c into debugmcp:main Aug 25, 2026
10 checks passed
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.

dev-proxy: hardcoded 120s build timeout makes docker rebuilds report a successful build as 'Build failed'

2 participants