#5182
#5155
#5094

1. The close(client) call is placed in the top-level http.HandlerFunc's defer, which means the channel is only closed when the entire HTTP request handler returns.
2. The actual event generation (l.{{.Call}}) runs in a separate threading.GoSafeCtx goroutine. When this goroutine finishes sending all events, the client channel remains open because close(client) is not executed within its scope.
3. The main for loop, which reads from the client channel, will then block indefinitely on case data := <-client: because it never receives a "closed" signal, even though no more events will be sent.
4. Furthermore, the case data := <-client: lacks an ok check, which is a standard Go practice to detect if a channel has been closed, preventing unnecessary processing of zero values.

This results in:

• Goroutine Leak: The main for loop goroutine remains active indefinitely, consuming resources, even after all events have been sent.
• Blocking Behavior: SSE connections do not terminate gracefully after event completion, holding clients in a waiting state.