Repository navigation
fix: decode CLIXML stderr at the WinRM executor - #113
Merged
Merged
Conversation
PowerShell remoting serializes progress/verbose/error streams as CLIXML on stderr. Undecoded, an exit-0 command whose only stderr is a 'Preparing modules for first use' progress record looks like a failure to agents and tests, and real errors arrive as unreadable XML. Decode at the source: progress/debug records are dropped, error/warning/verbose records become plain text, non-CLIXML stderr and malformed blobs pass through verbatim. Blob fixtures captured from a real 3DEXPERIENCE host on 2026-08-21. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Exit-0 commands over WinRM frequently return stderr containing only a CLIXML
progress blob ("Preparing modules for first use"), which reads as failure to
agents and shows up as raw XML in the fawdy UI. fawdy's bridge-side regex
strip was also being bypassed because Go's json.Marshal HTML-escapes angle
brackets (fixed separately in fawdy).
This decodes CLIXML in
winrmClient.Executeso every consumer gets plaintext: progress and debug records are dropped, error/warning/verbose string
records are decoded (including
_xHHHH_escapes), plain stderr passesthrough untouched, and malformed blobs are preserved verbatim rather than
swallowed. Fixtures in the tests are captured from a real 3DEXPERIENCE host.
🤖 Generated with Claude Code