aglinxinyuan opened a new pull request, #8435: URL: https://github.com/apache/texera/pull/8435
### What changes were proposed in this PR? Deletes `ExecutionStatusEnum.scala`, an 18-line file that holds the ASF license header and nothing else — no code, and no reference to the name anywhere in the tree. Pure deletion, no behaviour change: **−18 lines**, none of them compiled. Flagged as a follow-up in the #8396 review. ### History | | | | --- | --- | | **Introduced by** | #1351 (2021-10-27) — "Detach workflow execution from frontend with reconnection support" added the `sealed trait ExecutionStatusEnum` and its Jackson serializer/deserializer, carried by `WorkflowStateEvent`; #1423 (2022-02-01) reshaped it into a `sealed abstract class` carrying a `name` and a DB status `code` | | **Emptied by** | #1387 (2022-02-10) — "Web server workflow-related state refactoring" moved execution state to the protobuf `WorkflowAggregatedState`, changed `WorkflowStateEvent.state` to a `String`, and left this file as a single blank line instead of deleting it. #3415 (2025-05-03) later stamped the ASF header onto the empty file | Empty for about four and a half years. Like #8396, a file with zero compiled lines. ### Any related issues, documentation, discussions? Closes #8434 ### How was this PR tested? No tests to change — the file had no code and no spec referenced it. Locally, from the repo root with Java 17: - `sbt "WorkflowExecutionService/Test/compile"` — success. - `sbt "WorkflowExecutionService/scalafmtCheckAll" "WorkflowExecutionService/scalafixAll --check"` — clean. Verification, re-runnable by a reviewer: ``` git grep -n ExecutionStatusEnum # nothing, on main as well — the name survives only as the filename git ls-files | grep ExecutionStatusEnum # the one file on main; gone on this branch ``` ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Fable 5.1) -- 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]
