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

   ## Summary
   
   - validate Prometheus range-query steps with the supported ordered duration 
grammar
   - surface explicit provider error envelopes received inside successful SSE 
responses
   - skip malformed null records without discarding valid Tencent catalog 
results
   - preserve omitted Tencent ACL permissions during id-based partial updates
   
   ## Why these fixes are grouped
   
   This consolidates the previously closed PRs #2175, #2177, #2179, and #2186 
in response to contribution guideline #2107. The changes form one backend 
hardening pass for data crossing external provider boundaries, and each 
behavior is submitted together with focused regression coverage.
   
   ## Root cause and impact
   
   Several provider adapters trusted external syntax or payload shape too 
early: the metrics validator accepted duration forms rejected downstream, the 
SSE parser ignored structured provider failures, the Tencent catalog assumed 
every SDK item was non-null, and Tencent ACL partial updates replaced omitted 
permission values. These cases now fail predictably or preserve valid data 
instead of producing downstream errors, hiding provider failures, dropping 
complete pages, or changing ACL permissions unexpectedly.
   
   ## Validation
   
   - `mvn -B -ntp -f server/pom.xml 
-Dtest=MetricsServiceTest,OpenAiCompatibleLlmClientTest,TencentAclServiceTest,TencentCatalogServiceTest
 test` — 47 tests passed
   - `mvn -B -ntp -f server/pom.xml 
-Dtest=!CliAgentProviderTest,!ClaudeCodeAgentProviderTest test` — 1198 tests 
passed
   - Maven Checkstyle — 0 violations
   - `git diff --check`
   
   Closes #2174.
   Closes #2176.
   Closes #2178.
   Closes #2185.
   


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