You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 19, 2024. It is now read-only.
Problem description
The vantage6 server and nodes have a socket connection between them, via which events such as "this task just started/finished/crashed" and "this node just came online" are shared. The UI should connect to the socket channel so that they can also read these messages
Desired solution
connect to socket channel
Give alerts to significant events (same as old UI)
Option to kill tasks that are running (same as old UI)
Update node status of nodes showing on current page if they are going on/offline (same as old UI)
Update task status for tasks showing on current page (same as old UI)
We may be able to work around this and implement API polling mechanisms - this could be a quick way to get around implementing socket connection but this is preferred long term solution
Problem description
The vantage6 server and nodes have a socket connection between them, via which events such as "this task just started/finished/crashed" and "this node just came online" are shared. The UI should connect to the socket channel so that they can also read these messages
Desired solution
Give alerts to significant events (same as old UI)Option to kill tasks that are running (same as old UI)Additional context
In the old UI there is a socket.message.service and a socket-connect service.
The text was updated successfully, but these errors were encountered: