Fix dev-db socket server slot leak and add a wedge watchdog - #1744
Merged
Conversation
Contributor
Cloudflare previewTorn down — the PR is closed. |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-marketing | 7ac8253 | Commit Preview URL Branch Preview URL |
Aug 25 2026, 09:30 PM |
@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: |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-cloud | 7ac8253 | Aug 25 2026, 09:32 PM |
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.
Kills the last recurring CI e2e flake family: mid-shard the cloud dev DB stops answering new connections (every later test dies with
cloud signIn: callback set no session (500)/CONNECT_TIMEOUT 127.0.0.1:<db-port>), most recently in run 32897502744 (cloud 6of16).Two changes:
maxConnectionsslot burned per reap, until every new connection is answered with "Too many connections" while the process, port, and PGlite are all healthy. The handler is now dropped when it dispatches its terminal error. Regression test:reaped handlers release their connection slots(fails against the unpatched server).select 1); after 3 consecutive failures it logs the server's stats to the boot log, swaps in a fresh socket server on the same PGlite (state lives in PGlite; the front-end is stateless), and exits non-zero if restarts don't restore service so the boot supervisor reports an attributable cause instead of minutes of anonymous timeouts.Checks: lint, typecheck,
dev-db-socket-concurrency.node.test.ts(6/6), manual watchdog exercise (healthy boot silent; forced wedge → 3 probe failures → stats dump → bounded restarts).