releases/ClaudeMailbox
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 17 Wiki Activity

fix(server): set explicit connectionTimeout to bound long-poll sockets

Browse Source 
Fastify's default connectionTimeout is 0 (no timeout). With /v1/watch
holding requests open for up to 300s, an OS-level cap prevents a stuck
socket from persisting forever even if app-level cleanup misses a case.
Set just above the watch max so a healthy long-poll never races the
socket timeout.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Mika Kuns
2026-05-20 16:24:26 +02:00
parent 8169ebf4fe
commit bc53daf6e6
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
node/src/server.ts
View File

@@ -29,7 +29,10 @@ function readVersion(): string {
const ANONYMOUS_PATHS = new Set(["/v1/list", "/v1/peek"]); const ANONYMOUS_PATHS = new Set(["/v1/list", "/v1/peek"]);
export async function buildServer(cfg: DaemonConfig, store: MailboxStore): Promise<FastifyInstance> { export async function buildServer(cfg: DaemonConfig, store: MailboxStore): Promise<FastifyInstance> {
const app = Fastify({ logger: true }); const app = Fastify({
logger: true,
connectionTimeout: 310_000,
});
const version = readVersion(); const version = readVersion();
app.addHook("onRequest", async (req: FastifyRequest, reply: FastifyReply) => { app.addHook("onRequest", async (req: FastifyRequest, reply: FastifyReply) => {