/analyze endpoint swallows errors — no logging, generic error message

[vzegnameta]

/analyze endpoint swallows errors — no logging, generic error message

Description

The /analyze REST endpoint catches all exceptions but doesn't log them. The catch block at src/transports/http.ts:48-52 returns a generic {"error": "<message>"} response with no console.error, making it impossible to diagnose failures from server logs (e.g. Cloud Run, Docker).

Current behavior

} catch (error) {
    const message = error instanceof Error ? error.message : "Unknown error";
    res.writeHead(500, { "Content-Type": "application/json" });
    res.end(JSON.stringify({ error: message }));
}

• No stdout/stderr output on error
• Cloud Run logs show only POST 500 with no traceback
• Root cause is invisible without modifying the code

Proposed fix

Add console.error before the response:

} catch (error) {
    console.error("[/analyze] Error processing PDF:", error);
    const message = error instanceof Error ? error.message : "Unknown error";
    res.writeHead(500, { "Content-Type": "application/json" });
    res.end(JSON.stringify({ error: message }));
}

Impact

One-line change. No behavior change for API consumers — same response format. Server operators can now see the full error + stack trace in logs.

[valentinozegna]

Fixed in v1.2.2 (#38).

Added console.error and console.warn logging across three locations:

• src/transports/http.ts — console.error("[/analyze] Error processing PDF:", error) in the /analyze endpoint catch block
• src/server.ts — console.error("[analyze_pdf] Tool error:", error) in the MCP tool handler catch block
• src/service.ts — console.warn for token limit fallbacks (expected behavior, not errors): chunk splitting and fallback to chunked processing

All server-side failures now appear in Cloud Run / Docker logs with full stack traces. API response format is unchanged.