fix: merge parsedError + podFailureDescription so OOMKilled surfaces in errorMessage
When both a JSONL error (e.g. "killed") and a pod terminated reason (e.g. "OOMKilled") are present, join them with "; " so the richer pod classification is never silently dropped by the parsedError short-circuit. Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
@@ -549,8 +549,9 @@ export async function execute(ctx: AdapterExecutionContext): Promise<AdapterExec
|
||||
const podFailureDescription = podTerminatedReason
|
||||
? `Pod exited: ${podTerminatedReason}${synthesizedExitCode != null ? ` (exit ${synthesizedExitCode})` : ""}`
|
||||
: null;
|
||||
const errorParts = [parsedError, podFailureDescription].filter(Boolean);
|
||||
const fallbackErrorMessage =
|
||||
parsedError || podFailureDescription || firstStderrLine || `OpenCode exited with code ${synthesizedExitCode ?? -1}`;
|
||||
errorParts.join("; ") || firstStderrLine || `OpenCode exited with code ${synthesizedExitCode ?? -1}`;
|
||||
|
||||
return {
|
||||
exitCode: synthesizedExitCode,
|
||||
|
||||
Reference in New Issue
Block a user