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

   ### Which Issue(s) This PR Fixes
   
   Fixes #7022
   
   ### Brief Description
   
   Remember event serialization/ordinary INSERT failures in the sink. At 
finalization send one fixed non-secret warning to live observers and 
best-effort persist it for history. Record ai.timeline.persistence_failed in 
existing run diagnostic fields when there is no more informative provider 
error. Preserve the provider completion/failure and user Stop status, the 
unique-key exception backstop, and exactly one terminal frame. Update endSeq to 
include the diagnostic event. No blind INSERT retry, new schema, dependency or 
wire type.
   
   ### How Did You Test This Change?
   
   - Baseline fault-injection regressions fail because the run has no 
durability diagnostic or warning.
   - Java21 conversation suite: 214 tests passed; 0 Checkstyle violations. 
Final test-only import ordering followed by rerunning AiRunExecutorTest (25 
tests) and Checkstyle.
   - Regressions cover missing answer/terminal events, serialization failure, 
continuing database failures, one warning/terminal, no retries, private 
diagnostic suppression, provider error precedence and USER_STOP preservation.
   - git diff --check passed; all test sources compile.
   
   The warning/run metadata remains best effort: sustained DB outage or a crash 
can prevent its persistence. COMPLETED still means provider success, not 
guaranteed event durability. This change reports incomplete history; it does 
not recover already lost rows. Architecture docs record this distinction. Full 
backend suite and production fault tests were not run locally; CI runs full 
repository checks.
   
   ### Checklist
   
   - [x] One coherent change
   - [x] Conventional Commit; ...Test regression names
   - [x] Existing ASF headers retained
   - [x] No new dependencies, schema, frontend text or source files
   - [x] Failure policy and limitations documented


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