Refactor context handling in HandleCount and HandleReq functions
Some checks failed
Go / build (push) Has been cancelled
Go / release (push) Has been cancelled

- Updated context creation in HandleCount and HandleReq to use context.Background() instead of the connection context, isolating timeouts to prevent affecting long-lived websocket connections.
- Improved comments for clarity on the purpose of the context changes.
- bump version to v0.17.17
This commit is contained in:
2025-10-24 16:55:15 +01:00
parent da1119db7c
commit bc8a557f07
3 changed files with 9 additions and 7 deletions

View File

@@ -86,9 +86,10 @@ func (l *Listener) HandleReq(msg []byte) (err error) {
// user has read access or better, continue
}
var events event.S
// Create a single context for all filter queries, tied to the connection context, to prevent leaks and support timely cancellation
// Create a single context for all filter queries, isolated from the connection context
// to prevent query timeouts from affecting the long-lived websocket connection
queryCtx, queryCancel := context.WithTimeout(
l.ctx, 30*time.Second,
context.Background(), 30*time.Second,
)
defer queryCancel()