eugenegujing opened a new issue, #7311: URL: https://github.com/apache/texera/issues/7311
### Task Summary `amber/src/main/scala/org/apache/texera/amber/engine/architecture/coordinator/CoordinatorTimerService.scala` owns the two recurring timers that drive statistics collection: one for frontend status updates and one for runtime-statistics persistence. The class has no spec, and the coordinator specs that construct a `CoordinatorProcessor` all pass `CoordinatorConfig(None, None, None, None)`, which means only the interval-empty path is ever taken and no timer is ever scheduled in a unit test. The end-to-end tests happen to use `CoordinatorConfig.default`, so the timers do run there, but nothing asserts the scheduling decision, the message payload, the idempotence guard, the cancel-and-clear behavior, or the independence of the two handles. ### Task Type - [ ] Refactor / Cleanup - [ ] DevOps / Deployment / CI - [x] Testing / QA - [ ] Documentation - [ ] Performance - [ ] Other -- 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]
