Graceful shutdown and error handling for the web server #161

New issue

Closed

opened 2026-10-07 11:51:52 +00:00 by aniram · 0 comments

aniram commented

2026-10-07 11:51:52 +00:00

Owner

http.ListenAndServe(connStr, mainMux) currently ignores its returned error and has no timeouts, so a port conflict exits silently and slow clients can hold connections open.

Use an explicit http.Server with ReadHeaderTimeout, ReadTimeout, WriteTimeout and IdleTimeout.
Handle SIGINT/SIGTERM via signal.NotifyContext and call Shutdown with a deadline.
Return the error from run() and exit non-zero on failure.

Acceptance criteria:

Starting the server on an occupied port prints an error and exits with code 1.
SIGTERM lets in-flight requests finish.

http.ListenAndServe(connStr, mainMux) currently ignores its returned error and has no timeouts, so a port conflict exits silently and slow clients can hold connections open. Use an explicit http.Server with ReadHeaderTimeout, ReadTimeout, WriteTimeout and IdleTimeout. Handle SIGINT/SIGTERM via signal.NotifyContext and call Shutdown with a deadline. Return the error from run() and exit non-zero on failure. Acceptance criteria: - Starting the server on an occupied port prints an error and exits with code 1. - **SIGTERM lets in-flight requests finish.**

aniram added this to the 2027.1 milestone

2026-10-07 11:51:52 +00:00

aniram added this to the Release 2027.1 project

2026-10-07 11:51:52 +00:00

aniram referenced this issue

2026-10-07 11:54:02 +00:00

Split syncer from web app #139

aniram closed this issue

2026-10-07 18:21:50 +00:00