[miniflare] Force-close connections in InspectorProxyController dispose#13523
[miniflare] Force-close connections in InspectorProxyController dispose#13523petebacondarwin wants to merge 1 commit intomainfrom
Conversation
🦋 Changeset detectedLatest commit: 0bd94a8 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Codeowners approval required for this PR:
Show detailed file reviewers
|
|
The change is straightforward and correct. The LGTM |
|
✅ All changesets look good |
create-cloudflare
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-pool-workers
@cloudflare/workers-editor-shared
wrangler
commit: |
…ispose Fold in fix from PR #13523: call server.closeAllConnections() before server.close() so active HTTP keep-alive or WebSocket connections don't prevent the close callback from firing.
|
Folded into #13515 which now includes this fix ( |
…ispose Fold in fix from PR #13523: call server.closeAllConnections() before server.close() so active HTTP keep-alive or WebSocket connections don't prevent the close callback from firing.
…ispose Fold in fix from PR #13523: call server.closeAllConnections() before server.close() so active HTTP keep-alive or WebSocket connections don't prevent the close callback from firing.
…ispose Fold in fix from PR #13523: call server.closeAllConnections() before server.close() so active HTTP keep-alive or WebSocket connections don't prevent the close callback from firing.
…ispose Fold in fix from PR #13523: call server.closeAllConnections() before server.close() so active HTTP keep-alive or WebSocket connections don't prevent the close callback from firing.
…ispose Fold in fix from PR #13523: call server.closeAllConnections() before server.close() so active HTTP keep-alive or WebSocket connections don't prevent the close callback from firing.
InspectorProxyController.dispose()was callingserver.close()without first callingserver.closeAllConnections(). Active HTTP keep-alive or WebSocket connections would prevent theclosecallback from firing, hanging the dispose indefinitely and contributing towrangler devnot exiting on Ctrl-C.The same file's
#closeServer()method (used during port changes viasetOptions()) already usescloseAllConnections()— this bringsdispose()in line with that pattern.#closeServer()pattern in the same file; existing inspector proxy tests confirm no regression