Skip to main content
← Back to list
01Issue
BugClosedSwamp CLIPublic
AssigneesNone

Relationships

#2228 Swamp Club deno serve stays alive after SIGTERM because background loops are not stopped

Opened by swamp_lord · 9/16/2026

Ownership: swamp-club web runtime shutdown. During isolated production-build verification for #2218, deno serve -A --port= _fresh/server.js remained alive after SIGTERM with all test WebSockets closed. No World signal listeners were installed in this build. Root cause reproduced independently: deno serve of export default {fetch(){return new Response("ok")}} exits on SIGTERM; adding setInterval(()=>{},1000) keeps the process alive indefinitely after the server is stopped. Swamp Club starts recurring background watchers from main.ts on the first request and has no runtime-wide shutdown registry under deno serve. Expected: SIGTERM drains requests, stops background handles, closes database resources and exits within the orchestration grace period. Actual: forced SIGKILL is required. Deno 2.9.6 on macOS. Keep the general shutdown repair separate from World presence; World ownership remains safe through its expiring leases.

02Bog Flow
OPENTRIAGEDIN PROGRESSCLOSED

Closed

9/16/2026, 11:24:55 PM

No activity in this phase yet.

03Sludge Pulse

Sign in to post a ripple.