@telorun/http-server 0.15.1 → 0.15.2

package/CHANGELOG.md

@@ -1,5 +1,18 @@
 # @telorun/http-server
 
+## 0.15.2
+
+### Patch Changes
+
+- a33b8cc: Log mid-stream failures server-side. When a `mode: stream` route's stream throws
+  after the response headers are flushed, the failure can't reach Fastify's error
+  handler or a `catches:` entry, so it was previously silent for the operator (it
+  was only emitted as an `Http.Api.streamFailed` event, which nothing logs unless a
+  debug consumer is attached). The stream-error hook now also logs on the server's
+  request logger (the one `Http.Server.logger` configures) at `error` level with
+  the error, route, status, and MIME. Client-facing behaviour is unchanged.
+  - @telorun/http-dispatch@0.4.1
+
 ## 0.15.1
 
 ### Patch Changes

package/dist/http-api-controller.js

@@ -165,15 +165,28 @@ export class HttpServerApi {
                     return dispatchCatches(route.catches, { code: err.code, message: err.message, data: err.data }, requestContext, acceptHeader, this.ctx.moduleContext, this.ctx.validateSchema.bind(this.ctx), sink);
                 }
                 await span.settle("ok");
-                return dispatchReturns(route.returns, result, requestContext, acceptHeader, this.ctx.moduleContext, this.ctx.validateSchema.bind(this.ctx), sink, (err, errCtx) => this.ctx.emitEvent("Http.Api.streamFailed", {
-                    path: route.request.path,
-                    method: route.request.method,
-                    status: errCtx.status,
-                    mime: errCtx.mime,
-                    error: err instanceof Error
-                        ? { message: err.message, stack: err.stack, code: err.code }
-                        : { message: String(err) },
-                }));
+                return dispatchReturns(route.returns, result, requestContext, acceptHeader, this.ctx.moduleContext, this.ctx.validateSchema.bind(this.ctx), sink, (err, errCtx) => {
+                    // Headers are already flushed, so this failure can't reach Fastify's
+                    // error handler (which logs pre-stream throws) — log it here, on the
+                    // same request logger `logger:` configures, so a mid-stream failure
+                    // isn't silent server-side. The event below stays for debug tooling.
+                    reply.log.error({
+                        err,
+                        path: route.request.path,
+                        method: route.request.method,
+                        status: errCtx.status,
+                        mime: errCtx.mime,
+                    }, "Http.Api stream failed after response headers were flushed");
+                    return this.ctx.emitEvent("Http.Api.streamFailed", {
+                        path: route.request.path,
+                        method: route.request.method,
+                        status: errCtx.status,
+                        mime: errCtx.mime,
+                        error: err instanceof Error
+                            ? { message: err.message, stack: err.stack, code: err.code }
+                            : { message: String(err) },
+                    });
+                });
             },
         });
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@telorun/http-server",
-  "version": "0.15.1",
+  "version": "0.15.2",
   "description": "Telo HTTP Server module - HTTP server and API resource kinds for Telo manifests.",
   "keywords": [
     "telo",
@@ -55,7 +55,7 @@
     "@types/node": "^20.0.0",
     "typescript": "^5.0.0",
     "vitest": "^2.1.8",
-    "@telorun/sdk": "0.38.0"
+    "@telorun/sdk": "0.44.0"
   },
   "peerDependencies": {
     "@telorun/sdk": "*"

package/src/http-api-controller.ts

@@ -222,8 +222,22 @@ export class HttpServerApi implements ResourceInstance {
           this.ctx.moduleContext,
           this.ctx.validateSchema.bind(this.ctx),
           sink,
-          (err, errCtx) =>
-            this.ctx.emitEvent("Http.Api.streamFailed", {
+          (err, errCtx) => {
+            // Headers are already flushed, so this failure can't reach Fastify's
+            // error handler (which logs pre-stream throws) — log it here, on the
+            // same request logger `logger:` configures, so a mid-stream failure
+            // isn't silent server-side. The event below stays for debug tooling.
+            reply.log.error(
+              {
+                err,
+                path: route.request.path,
+                method: route.request.method,
+                status: errCtx.status,
+                mime: errCtx.mime,
+              },
+              "Http.Api stream failed after response headers were flushed",
+            );
+            return this.ctx.emitEvent("Http.Api.streamFailed", {
               path: route.request.path,
               method: route.request.method,
               status: errCtx.status,
@@ -232,7 +246,8 @@ export class HttpServerApi implements ResourceInstance {
                 err instanceof Error
                   ? { message: err.message, stack: err.stack, code: (err as { code?: string }).code }
                   : { message: String(err) },
-            }),
+            });
+          },
         );
       },
     });