Repository navigation
front kit: a one-shot answer's stdout is base64 - #647
Merged
Merged
Conversation
The kit judged a one-shot answer by finding the marker in `stdout` as plain text. Since #601 every exec answer carries `stdout` and `stderr` as standard base64, so a correct answer (`{"exit_code":0,"stdout":"b2stLi4="}`) was broken for not being plain text. The kit now decodes `stdout` before looking for the marker; bytes that are not base64 count as not-ran. The in-repo reference front's one-shot body is base64 too, and a new fault mode answers a malformed `stream` one-shot, so the reference run covers a successful one-shot answer. Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LBGuEqSTj8eEfjuLH6GSmD
jaredLunde
enabled auto-merge
October 31, 2026 19:16
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since #601 every exec answer carries `stdout` and `stderr` as standard base64, but the front conformance kit still searched a one-shot answer's `stdout` as plain text. A correct answer such as `{"exit_code":0,"stdout":"b2stLi4="}` therefore failed the "a refused extension is 400 or 422" check (case `stream`).
The kit now decodes `stdout` before looking for the marker, and bytes that are not base64 count as not-ran. The in-repo reference front's one-shot body is base64 too, and a new fault mode (`OneShotStreamAnswers`) answers a malformed `stream` one-shot, so the reference run covers a successful one-shot answer.
Test: `cargo test -p beyond-agent --test it exec_front_conformance` (6 passed, 0 failed). `cargo clippy -p beyond-agent --tests`: no warnings. `cargo fmt --check`: clean.
🤖 Generated with Claude Code