Michelle/redlight
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 18 Wiki Activity

fix: log underlying network error cause for failed transcription requests
Build & Push Docker Image / build (push) Successful in 4m5s
Details

Browse Source 
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Michelle
2026-07-14 12:30:17 +02:00
co-authored by Claude Opus 4.8
parent 51b42cfee5
commit 4aeca36a9c
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
server/config/transcription.js
+4 -1
View File
@@ -62,7 +62,10 @@ export async function requestTranscription({ meetingId, recordingId, prompt }) {
log.server.info(`Transcription requested for recording ${recordingId} (meeting: ${meetingId})`); log.server.info(`Transcription requested for recording ${recordingId} (meeting: ${meetingId})`);
return true; return true;
} catch (err) { } catch (err) {
log.server.error(`Transcription request error: ${err.message}`); // undici wraps the real network error (ECONNREFUSED, ENOTFOUND, timeout, …)
// in err.cause — surface it, "fetch failed" alone is undiagnosable.
const cause = err.cause ? ` (${err.cause.code || ''} ${err.cause.message || ''})`.trimEnd() : '';
log.server.error(`Transcription request to ${url} failed: ${err.message}${cause}`);
return false; return false;
} }
} }