You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 6e062ae
Browse filesBrowse the repository at this point in the historyBrowse files
fix(exec): explain Session workspace mismatches instead of suggesting a retry (#584)
mcode exec appended "Retry after the connection recovers." to every runtime
failure, including Session errors that can never succeed on retry. A resumed
Session whose workspace differs from --cwd now names the Session workspace and
the --cwd to use; archived Sessions and a missing --continue target also say
what to do next. These errors are marked non-retryable, keep exit code 4 and
category runtime, and failed results with retryable: false no longer get the
retry hint.
Document in the Python SDK README and resume_thread docstrings that a resumed
Session must use the cwd it was created with.
if(!error.retryable)returnasSentence(`The run failed: ${tuiErrorDiagnostic(error)}`);
23
24
return`The run failed: ${tuiErrorDiagnostic(error)}. Retry after the connection recovers.`;
24
25
}
25
26
return`MCode encountered an internal error: ${tuiErrorDiagnostic(error)}. Retry; if it keeps happening, report it through an available support channel.`;
@@ -43,5 +44,10 @@ export function formatTuiExecResultFailure(result: ExecResult): string {
0 commit comments