The GitHub Actions job "Required Checks" on texera.git/gh-readonly-queue/main/pr-6729-5042d96ec85d98ed18bde841b2e74922c43f5c3b has failed. Run started by GitHub user Xiao-zhen-Liu (triggered by Xiao-zhen-Liu).
Head commit for run: 306d627b906b519ea0c51fd2daa6cb9b3a877444 / Xiaozhen Liu <[email protected]> feat(amber): carry cache-reuse status as a metrics flag (#6729) ### What changes were proposed in this PR? This PR was reworked after the discussion in #5880. The old version added a new CACHE_REUSED state; the review threads below refer to that version. The discussion concluded that a reused operator should just report COMPLETED, because every place that checks state treats completed and reused the same way. What still needs to travel is one bit: whether the operator's results came from the cache. So the PR now adds only that bit: - A `reused_from_cache` boolean on `OperatorMetrics`. A reused operator still reports COMPLETED. - A logical operator counts as reused only when all of its physical operators are (`aggregateMetrics`). - The statistics websocket event and the TS `OperatorStatistics` type carry the flag to the frontend. No UI changes here; that is #5886. Nothing sets the flag yet. The producer comes with #5884, so with an empty cache the engine behaves exactly like main. ### Any related issues, documentation, discussions? Closes #5883. Part of #5881. Design discussion: #5880. Related: #5884. ### How was this PR tested? New unit tests in ExecutionUtilsSpec cover the all-physical-operators rule and the flag staying false when nothing sets it. Existing specs pass unchanged, scalafmt is clean, and the frontend production build passes. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude (Claude Code) Report URL: https://github.com/apache/texera/actions/runs/34804516373 With regards, GitHub Actions via GitBox
