pilichoumao opened a new issue, #6395:
URL: https://github.com/apache/rocketmq-dashboard/issues/6395

   ### Studio Version
   
   `rocketmq-studio@779b8c0e7aed2396d3cc72743dcd544ea48e9ae6`, built from 
source.
   
   ### Runtime Environment
   
   macOS, Go 1.27.1. This is a standalone rmqctl output issue; a broker or 
database is not required for the config reproduction.
   
   ### Actual Behavior
   
   `Rows` escapes TAB/LF/CR in string values after #4661, but other table entry 
points bypass that escaping. A valid stored context name containing LF/TAB 
makes `config get-contexts` print extra rows/columns. Dynamic table headers and 
mutation metadata have the same gap. In normal row values, VT becomes padding, 
FF becomes a row break, and ESC is emitted raw.
   
   ### Steps to Reproduce
   
   ```bash
   rmqctl --config /private/config.yaml config set-context $'dev\nforged\trow' \
     --server https://studio.example.com --access-key-env AK --secret-key-env SK
   rmqctl --config /private/config.yaml config get-contexts
   ```
   
   Use an existing private directory (0700) for the config file. The single 
context produces more than one data line. Regression tests also pass VT/FF/ESC 
through a real HTTP Result envelope and the App's table output.
   
   ### Expected Behavior
   
   All table cells, including headers, config fields and mutation metadata, 
should show ASCII C0/DEL as visible escapes. Stored config and JSON/YAML values 
should retain their original content, and ordinary UTF-8 and literal 
backslashes should keep their display.
   
   ### Scope / Related Contributions
   
   This completes the table-cell boundary started by #4661. Open #5624 
addresses terminal display width; its production patch still reproduces these 
cases. This issue does not propose changing width, authentication, confirmation 
or the JSON/YAML contract.
   


-- 
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