pilichoumao opened a new pull request, #6899:
URL: https://github.com/apache/rocketmq-dashboard/pull/6899

   ### Which Issue(s) This PR Fixes
   
   Fixes #6895.
   
   ### Brief Description
   
   A JSON-decoded API error or a local MCP transport error can print ESC, BEL, 
backspace and other ASCII controls directly to stderr. Escape C0/DEL at the 
plain CLI error and MCP stderr boundaries. Keep the existing CR/LF/TAB 
flattening, Unicode and literal backslashes, and retain the decoded values of 
JSON/YAML/MCP errors. Apply the stdio byte cap after display escaping.
   
   This complements the table-cell fix #6396. It does not include #6317's 
output-write behavior; the two changes were also tested together in a temporary 
composition.
   
   ### How Did You Test This Change?
   
   Linux x86_64, Go 1.27.1, based on `rocketmq-studio` at 
`a92c23144408cdf5729707050e9ecd9b75f1bad0`.
   
   - The same new regressions on unchanged production fail for HTTP diagnostic 
controls, stdio request/notification stderr, and the ESC byte-limit case. 
Ordinary Unicode, literal backslashes, CR/LF/TAB, structured JSON/YAML and 
UTF-8 boundary controls pass.
   - `make -C rmqctl ci`: full race suite, gofmt, catalog consistency, go vet, 
all six cross-platform binaries, and per-binary license generation/verification 
pass.
   - Temporary composition with #6317: the complete cmd race suite passes.
   - Focused command tests pass locally; `git diff --check` passes.
   
   HTTP tests use a local httptest peer and the actual App command; no live 
Studio/Broker, Java/MySQL or frontend integration is claimed.
   
   ### Checklist
   
   - [x] One coherent fix, Conventional Commit, Go regressions with ASF header
   - [x] Behavior documented; no new dependencies or UI text
   
   AI assistance was used to investigate, implement and validate this change.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to