User Request
Type: bug
Target: Console Application
Submitted by: @aashu2006
Console Request ID: d156ecd0-dfdf-45ae-9b1b-5047f367017f
Description
What happened:
In pkg/api/server.go:1301-1338, Server.Shutdown() calls hub.Close(), k8sClient.StopWatching(), bridge.Stop(), store.Close(), and app.Shutdown() but never calls StopSSECacheEvictor(). The function's docstring explicitly says it is "Intended for server shutdown" but it is never invoked. The evictor goroutine runs indefinitely after server shutdown.
What I expected:
StopSSECacheEvictor() should be called in Server.Shutdown() alongside the other cleanup calls.
Steps to reproduce:
- Start the server and trigger any SSE stream (populates the cache)
- Shut down the server
- Observe the SSE cache evictor goroutine continues running after shutdown
This issue was automatically created from the KubeStellar Console.
User Request
Type: bug
Target: Console Application
Submitted by: @aashu2006
Console Request ID: d156ecd0-dfdf-45ae-9b1b-5047f367017f
Description
What happened:
In
pkg/api/server.go:1301-1338,Server.Shutdown()callshub.Close(),k8sClient.StopWatching(),bridge.Stop(),store.Close(), andapp.Shutdown()but never callsStopSSECacheEvictor(). The function's docstring explicitly says it is "Intended for server shutdown" but it is never invoked. The evictor goroutine runs indefinitely after server shutdown.What I expected:
StopSSECacheEvictor()should be called inServer.Shutdown()alongside the other cleanup calls.Steps to reproduce:
This issue was automatically created from the KubeStellar Console.