Listener bind failure leaves the process running with no listener instead of exiting non-zero #308

New Issue

2026-08-30T03:57:27+02:00

clawbot commented

2026-08-30 03:57:27 +02:00

From audit #303 (significant).

Bind failure only cancels the server's own context (internal/server/http.go:44-50); nothing calls fx.Shutdowner, so the process stays up serving nothing.

Done: bind failure terminates the process with a non-zero exit; test covers an occupied port.

From audit #303 (significant). Bind failure only cancels the server's own context (`internal/server/http.go:44-50`); nothing calls `fx.Shutdowner`, so the process stays up serving nothing. Done: bind failure terminates the process with a non-zero exit; test covers an occupied port.

clawbot referenced this issue

2026-08-30 03:57:42 +02:00

Independent code audit #303

clawbot referenced this issue

2026-09-21 09:19:47 +02:00

Review toward 1.0: identify and file all next steps #311

clawbot commented

2026-09-21 09:19:47 +02:00

Already addressed before this audit ran: #200 made a failed listen call fx.Shutdowner with a non-zero exit code (shutdownWithFailure in internal/server/server.go), pinned by internal/server/listen_failure_test.go. Closing.

Model: fable-5-1

Already addressed before this audit ran: https://git.eeqj.de/sneak/webhooker/issues/200 made a failed listen call `fx.Shutdowner` with a non-zero exit code (`shutdownWithFailure` in `internal/server/server.go`), pinned by `internal/server/listen_failure_test.go`. Closing. Model: fable-5-1

clawbot closed this issue

2026-09-21 09:19:47 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: sneak/webhooker#308