Synchronous channel cleanup

Abierto
#3,064 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
haskell

Línea de trabajo

Start by reading the channel shutdown and stream worker code to find where ThreadAbort is sent; the issue does not name specific files or tests. Compare synchronous cancellation, asynchronous abort, and the proposed timeout based hybrid, then identify the behavior and configuration that should be tested. Done means the chosen shutdown mode is implemented and its effect on the current stream action and pending items is verified.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

We throw ThreadAbort exception to running thread when the channel is stopped. Asynchronous exceptions can cause inadvertent problems because of unclean shutdown of the thread. It may leave the system in inconsistent state unless proper exception handling is implemented by the programmer. To avoid such issues we can also use a synchronous shutdown of streams by setting a flag and letting the thread abort itself. This would stop the thread before the next item in the stream is handled but the current action would not be interrupted. This could lead to delays in aborting the streams but would be safer than async signalling. This could be a config option, perhaps the default and the programmer can choose the other way if needed.

We can also have an option of a hybrid approach where we try to stop the threads synchronously first then after a timeout throw async exceptions.

Lenguaje dominante
Haskell
Estrellas
926
Forks
71
Merge medio
6 h 49 min
PR fusionados (30 d)
3

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 composewell/streamly

Todos los issues de composewell/streamly

Issues similares

Más issues de Haskell

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.