Repository navigation
Conversation
The connected-node SSH wrapper mis-escapes inner single quotes, so both commands died with 'unexpected EOF while looking for matching' before any code was checked (nights 2026-10-18/19 INCONCLUSIVE). Equivalent spellings with no quote characters. Co-Authored-By: jjohare <github@thedreamlab.uk>
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
2 participants
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.
The connected-node adapter's SSH wrapper mis-escapes single quotes inside evaluator commands (the quote becomes a doubled quote and bash fails with 'unexpected EOF'), so the fmt and doc evaluators reported BLOCKED-ENV or INCONCLUSIVE on the HP annexe.
This keeps the two evaluator commands in
dream.config.jsonquote-free until the adapter passes argv. The adapter-side quoting fix is tracked separately in agentbox.🤖 Generated by Claude Code