yuluo-yx opened a new pull request, #1794:
URL: https://github.com/apache/rocketmq-dashboard/pull/1794

   ## What is the purpose of the change
   
   Encode normal and transactional topic message bodies deterministically. 
Platform-default `String.getBytes()` corrupted non-ASCII text when the JVM 
default charset was not UTF-8.
   
   Fixes #1789
   
   ## Brief changelog
   
   - Use `StandardCharsets.UTF_8` in both send paths.
   - Verify both paths under an ISO-8859-1 JVM default.
   
   ## Verifying this change
   
   - JDK: Temurin 17.0.19
   - Focused backend Maven compile and test phases completed
   - `TopicServiceImplTest`: 2 focused tests, 0 failures, 0 errors
   - `mvn validate`: passed
   - `git diff --check`: passed
   - PR scope check: passed (2 files, 14 changed lines, one commit, base 
`master`)
   - Full lifecycle, integration, E2E, and container checks were not run 
because this five-PR workflow requires lightweight local verification and 
leaves heavyweight checks to upstream CI.
   
   Follow this checklist to help us incorporate your contribution quickly and 
easily.
   
   - [x] Make sure there is a Github issue filed for the change. This PR 
addresses only that issue.
   - [x] Format the pull request title like `[ISSUE #123] Fix UnknownException 
when host config not exist`. Each commit has a meaningful subject and body.
   - [x] Write a pull request description that explains what, how, and why.
   - [x] Write necessary unit tests to verify the logic correction.
   - [ ] Run the repository full basic, install, and integration command 
matrix. The focused backend checks above pass; heavyweight checks are delegated 
to upstream CI.
   - [ ] If this contribution is large, file an Apache Individual Contributor 
License Agreement.


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