Make Zeno to be signalable by HQ via websocket#429
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #429 +/- ##
==========================================
- Coverage 54.69% 54.28% -0.41%
==========================================
Files 120 120
Lines 7345 7400 +55
==========================================
Hits 4017 4017
- Misses 3004 3059 +55
Partials 324 324
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Pull Request Overview
This PR adds websocket message handling capabilities to Zeno, allowing it to receive and process signals from HQ. The implementation enables HQ to remotely control Zeno processes by sending signal commands through the websocket connection.
- Adds a new message listening goroutine that processes incoming websocket messages
- Implements message dispatching based on message type with initial support for "signal" messages
- Adds signal handling functionality that allows sending Unix signals to the current process
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
NGTmeaty
left a comment
There was a problem hiding this comment.
Some quick comments - and a question - if the HQ implementation does not support websocket are we going to panic or continue trying to connect?
b441660 to
b6376a4
Compare
6648fbd to
2ac2f9e
Compare
* Make Zeno to be signalable by HQ via websocket * check the error returned by dispatchMessageByType * chore: WARN with the additional info * add readTimeout

No description provided.