Caideyipi opened a new pull request, #19066:
URL: https://github.com/apache/iotdb/pull/19066

   ## Description
   
   Chinese builds still emit English diagnostics when inline format templates, 
helper arguments, and stored message variables bypass the compile-time message 
classes. Route 541 diagnostic sites through paired EN/ZH constants across Pipe 
API, subscription, CLI schema tools, node-commons, ConfigNode, and DataNode, 
adding 462 message keys.
   
   The changes cover pipe validation and transfer errors, subscription polling 
and lifecycle errors, write/storage diagnostics, TsFile loading errors, and 
schema/metadata operations. Preserve the original English text, format 
arguments, status codes, and exception causes. Keep machine-facing identifiers 
and existing text-based classifiers unchanged, and use the Chinese 
missing-broker wording already recognized by subscription clients.
   
   ## Validation
   
   - Spotless applied to all six changed modules with `with-integration-tests`.
   - Static checks passed for EN/ZH key parity, format-specifier order, exact 
English text reuse, and message-only Java substitutions.
   - Remote JDK 17: clean full-reactor EN package and 75 existing unit tests 
across 10 test classes; zero failures or skipped tests.
   - Remote JDK 17: clean full-reactor ZH package with test compilation 
(`with-zh-locale`, `skipTests`).
   - Each locale used clean source and a separate fresh Maven repository, with 
matching TsFile dependencies rebuilt from source.
   
   The unit-test selection includes subscription status/lifecycle/connection 
handling, `SubscriptionInfoTest`, `TabletStatementConverterTest`, 
`LoadTsFileConsensusNodeTest`, `SettleRequestHandlerTest`, and the three 
modules' `TypeServicesTest` classes. No tests were added or modified.
   


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