Attach a diagnosis to the dev-db socket wedge timeouts - #1767
Draft
RhysSullivan wants to merge 4 commits into
Draft
Attach a diagnosis to the dev-db socket wedge timeouts#1767RhysSullivan wants to merge 4 commits into
RhysSullivan wants to merge 4 commits into
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-cloud | e3ff346 | Aug 28 2026, 03:14 AM |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-marketing | e3ff346 | Commit Preview URL Branch Preview URL |
Aug 28 2026, 03:15 AM |
Contributor
Cloudflare preview
Sign-in is Cloudflare Access (one-time PIN to an allowed email). The preview has its own database and encryption key; it is destroyed when this PR closes. |
@executor-js/cli
@executor-js/config
@executor-js/execution
@executor-js/sdk
@executor-js/codemode-core
@executor-js/runtime-quickjs
@executor-js/plugin-file-secrets
@executor-js/plugin-graphql
@executor-js/plugin-keychain
@executor-js/plugin-mcp
@executor-js/plugin-onepassword
@executor-js/plugin-openapi
executor
commit: |
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.
Diagnostics for the two distinct dev-db wedge families, so the next occurrences carry their own cause.
Unit-suite wedges (runs 32933818134, 33019527020): the reap and ghost scenarios each wedged once as bare 30s vitest timeouts — bystander startup served, query then hung. ~800 isolated replays (macOS + Linux, idle and CPU-starved) never reproduced it. The two bystander queries now run under a 20s deadline that fails with the server's queue/handler stats plus a fresh-startup probe (a latched queue serves nobody; per-handler pinning still answers new startups).
E2E-shard cascades (latest: run 33129376530, main): 100+ seconds of app-side
CONNECT_TIMEOUTagainst the dev DB while every watchdog probe from the dev-db process silently PASSED — the server was healthy and the stall is on the app's side of the socket (the workerd/miniflare outbound path), which a silent-when-healthy watchdog cannot show. The watchdog now logs a stats heartbeat (every 60s, and on every 50-connection jump in active connections), so the next cascade's boot log shows whether connections pile up before the starvation — the direct test of the workerd-socket-leak theory.Pure observability in both cases — no behavior or assertion changes.
Checks: lint, typecheck, the socket suite (6/6), dev-db boot smoke.