Skip to content

fix(web): explain Bash exit 127 in session transcripts - #398

Merged
BaaRai merged 4 commits into
BaaRai:mainfrom
YunzhouLi-hub:fix/show-bash-exit-127
Nov 20, 2026
Merged

BaaRai merged 4 commits into
BaaRai:mainfrom
YunzhouLi-hub:fix/show-bash-exit-127

Conversation

@YunzhouLi-hub

Copy link
Copy Markdown
Contributor

Summary

Show an operator-facing diagnostic when a failed Bash result in the session transcript reports exit code 127. The diagnostic points to the command or its interpreter and leaves the recorded result visible. It uses the final exit-status marker in both framed and plain results. A quoted marker, incomplete frame, or different exit status does not trigger the hint.

Refs #339 (transcript diagnostics). This is limited to the operator view. Tool availability, tool selection, and retry behavior are outside this change.

Validation

  • node --test src/lib/bash-exit-status.test.mjs passed all three tests.
  • node scripts/check-i18n.mjs passed.
  • TypeScript tsc --noEmit --incremental false and git diff --check passed.

@BaaRai

BaaRai commented Nov 20, 2026

Copy link
Copy Markdown
Owner

Thanks. The helper and its test look right; I ran the test locally and all three cases pass. The issue is that nothing runs it in CI: test:i18n only runs check-i18n.mjs, and the other test:* scripts do not include bash-exit-status.test.mjs. Please wire it into web/package.json (extend test:i18n or add a dedicated script) so the web job actually executes it. Then this is ready.

@BaaRai
BaaRai merged commit 026213f into BaaRai:main Nov 20, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants