User Request
Type: bug
Target: Console Application
Submitted by: @aashu2006
Console Request ID: 169b2a12-8057-4120-87a6-6bc6cbada2e5
Description
What happened:
In pkg/api/handlers/exec.go:405, the exec_started message write error is explicitly discarded with _ = c.WriteMessage(websocket.TextMessage, startMsg). If the write fails the handler continues into executor.StreamWithContext, giving the client no notification and proceeding with a broken pipe.
What I expected:
The write error should be checked — if it fails the handler should return early rather than continuing into the exec stream.
Steps to reproduce:
- Close the WebSocket connection just before exec starts
- Observe the handler continues into StreamWithContext despite the failed write
This issue was automatically created from the KubeStellar Console.
User Request
Type: bug
Target: Console Application
Submitted by: @aashu2006
Console Request ID: 169b2a12-8057-4120-87a6-6bc6cbada2e5
Description
What happened:
In
pkg/api/handlers/exec.go:405, the exec_started message write error is explicitly discarded with_ = c.WriteMessage(websocket.TextMessage, startMsg). If the write fails the handler continues intoexecutor.StreamWithContext, giving the client no notification and proceeding with a broken pipe.What I expected:
The write error should be checked — if it fails the handler should return early rather than continuing into the exec stream.
Steps to reproduce:
This issue was automatically created from the KubeStellar Console.