Sample
Close active client connections and drain in-flight requests in Bun.serve using server.stop(true) rather than default server.stop()
sha256:6c2fe1687f1cc5644493b0d27863b582aded1f946d1f89d49c2501a53f798000
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Close active client connections and drain in-flight requests in Bun.serve using server.stop(true) rather than default server.stop() HOW
- Packages
- bun 1.3.14
- Environment
- node
- Created
- 2026-08-17T03:16:02Z
Commonly assumed
Calling server.stop() on a Bun.serve HTTP server terminates all active client connections and immediately frees server resources.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- Calling server.stop() without arguments retains active in-flight connections and leaves server.pendingRequests non-zero until server.stop(true) is explicitly invoked.
- assert server.pendingRequests is 1 while an in-flight request is being processed by the fetch handler
- assert calling server.stop() leaves server.pendingRequests at 1 and preserves active client connection
- assert calling server.stop(true) forcefully terminates active client connections and reduces server.pendingRequests to 0
Files
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9