aglinxinyuan opened a new issue, #7778: URL: https://github.com/apache/texera/issues/7778
### Task Summary `ReportCurrentProcessingTuple` is a `ClientEvent` with neither a producer nor a consumer. Both sides of the channel were enumerated on current `main`: - **Producers** — every `sendToClient(...)` argument type in `amber/src/main`: `ExecutionStateUpdate`, `ExecutionStatsUpdate`, `FatalError`, `OperatorPortResultUriAvailable`, `RuntimeStatisticsPersist`, `UpdateExecutorCompleted`, `WorkerAssignmentUpdate`, plus `ConsoleMessage`/`EmptyReturn`. `ReportCurrentProcessingTuple` is not among them. - **Consumers** — `ClientActor` dispatches `ClientEvent`s through `ClassTag`-keyed `registerCallback` handlers. Every registration in `amber/src/main` is for `ConsoleMessage`, `ExecutionStateUpdate`, `ExecutionStatsUpdate`, `FatalError`, `OperatorPortResultUriAvailable`, `RuntimeStatisticsPersist`, `UpdateExecutorCompleted`, `WorkerAssignmentUpdate` or `WorkflowRecoveryStatus`. None is for this type. So nothing can construct it and nothing would receive it if something did. Its only references are the declaration and two round-trip serde tests added during the 2026 coverage work. Removing it also frees the `core.tuple.Tuple` import in `ClientEvent.scala`, which no other event in that file uses. Pure deletion, no behaviour change: −42 lines. ### Task Type - [x] Refactor / Cleanup -- 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]
