Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Remove the empty ExecutionStatusEnum.scala

Cerrado
#8,434 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@aglinxinyuan ya está trabajando en esto.

Desde el 5/9/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Task Summary

amber/src/main/scala/org/apache/texera/web/model/websocket/event/ExecutionStatusEnum.scala is an 18-line file that holds the ASF license header and nothing else — no code, and nothing in the tree references the name. git grep -n ExecutionStatusEnum returns nothing at all; it survives only as a filename. Flagged as a follow-up in the #8396 review.

Introduced by #1351 (2021-10-27, "Detach workflow execution from frontend with reconnection support") as a sealed trait ExecutionStatusEnum with a hand-written Jackson serializer/deserializer, carried by WorkflowStateEvent; #1423 (2022-02-01, "Track metadata information about workflow executions") 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"), which 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, "Add ASF header and RAT CI") then stamped the license header onto the empty file, which is all it has held since.

Empty for about four and a half years. Like the MockKillWorkerResource removal in #8396, a file with zero compiled lines.

Pure deletion, no behaviour change: −18 lines.

Task Type
  • Refactor / Cleanup
  • DevOps / Deployment / CI
  • Testing / QA
  • Documentation
  • Performance
  • Other
Lenguaje dominante
Scala
Estrellas
321
Forks
192
Merge medio
3 d 7 h
PR fusionados (30 d)
145

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apache/texera

Todos los issues de apache/texera

Issues similares

Más issues de Scala

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.