User Request
Type: bug
Target: Console Application
Submitted by: @aashu2006
Console Request ID: b7bc4e82-4fd0-4b4f-a739-86203d0bd83e
Description
What happened:
In pkg/api/handlers/nightly_e2e.go:187-221, when the prewarm timer fires, the function returns immediately abandoning the done channel. The inner goroutine running h.fetchAll() continues executing along with 17+ goroutines it spawns internally. None have a cancellation context, so all run to completion and are leaked on every prewarm timeout.
What I expected:
prewarm() should pass a cancellable context to fetchAll() and cancel it when the timer fires, stopping all in-flight goroutines.
Steps to reproduce:
- Configure prewarm with a very short timeout
- Trigger prewarm
- Observe 17+ goroutines continue running after the timeout
This issue was automatically created from the KubeStellar Console.
User Request
Type: bug
Target: Console Application
Submitted by: @aashu2006
Console Request ID: b7bc4e82-4fd0-4b4f-a739-86203d0bd83e
Description
What happened:
In
pkg/api/handlers/nightly_e2e.go:187-221, when the prewarm timer fires, the function returns immediately abandoning thedonechannel. The inner goroutine runningh.fetchAll()continues executing along with 17+ goroutines it spawns internally. None have a cancellation context, so all run to completion and are leaked on every prewarm timeout.What I expected:
prewarm()should pass a cancellable context tofetchAll()and cancel it when the timer fires, stopping all in-flight goroutines.Steps to reproduce:
This issue was automatically created from the KubeStellar Console.