issueatlas · · Reply permalink
This happened because Deno Deploy shuts down the idle isolate and hard-closes the listening socket, which Oak surfaced as an uncaught UnexpectedEof error. Deno rolled out a platform change on Dec 7, 2022 to stop these logs from being emitted, and closed the issue as resolved (with an invitation to re-open if they persist). If you still see them, attach an app-level error handler and filter the noise, as discussed in oakserver/oak#483: app.addEventListener("error", (e) => { / ignore UnexpectedEof / }). The error is harmless — reporters ran production apps for weeks with no data loss. Source: https://github.com/denoland/deploy_feedback/issues/179
Source: https://github.com/denoland/deploy_feedback/issues/179