Calling Miniflare#dispose() a second time rejects with ERR_SERVER_NOT_RUNNING, causing skipped cleanup steps.
Calling Miniflare#dispose() a second time rejects with ERR_SERVER_NOT_RUNNING, causing skipped cleanup steps.
Problem statement normalized from the linked evidence
CANDIDATE VIEW · NOT A PUBLISHED OPPORTUNITY
01
Qualification checklist
Gate decision: Aug 15, 2026
×
At least 3 independent users2 / 3
NOT MET
×
At least 2 independent discussions1 / 2
NOT MET
×
At least 1 supporting signal1 Workarounds
NOT MET
02
Observed signals
Users2
Discussions1
Mentions2
Active days1
Source coverageGitHub
TrendUNKNOWN
First seenAug 09, 2026
Last seenAug 09, 2026
Why the gate is holding
Fewer than 3 independent users
Fewer than 2 independent discussions
No supporting growth, persistence, intent, workaround, alternative, blocked-workflow, or cross-source signal
Competition research, commercial scoring, and Build Gap analysis do not run until this gate passes.
03
Source evidence
2 evidence records
github · MEDIUM · Aug 09, 2026
cloudflare/workers-sdk
> [!NOTE] > This is an automated, advisory triage report generated by workers-devprod. It is not an official maintainer response — a maintainer will follow up. 🤖 Automated triage report # Issue Triage: cloudflare/workers-sdk#15097 ## Summary `Miniflare#dispose()` is not idempotent: a second call rejects with `ERR_SERVER_NOT_RUNNING` and aborts the rest of the teardown, leaking the dev registry file watcher, Hyperdrive proxy servers, and the instance registry entry. ## Classification - **Type:** Bug - **Component:*…
Miniflare#dispose() rejects with ERR_SERVER_NOT_RUNNING when called twice, skipping the rest of its cleanup
### What versions & operating system are you using? `miniflare` 5.20260801.1-alpha (reproduced against `main` @ 6dbd192f1), Node v24.14.1, macOS 15. ### Please provide a link to a minimal reproduction Inline below — six lines, no config or account needed. ### Describe the Bug Calling `Miniflare#dispose()` a second time rejects with `ERR_SERVER_NOT_RUNNING` ("Server is not running."). `dispose()` has no "already disposed" guard, so a second call re-runs the whole teardown sequence. Two of those steps close a Node HT…