cylc-uiserver
cylc-uiserver copied to clipboard
cylc
A Jupyter Server extension that serves the cylc-ui web application for monitoring and controlling Cylc workflows.
Sometimes workflows die in nasty ways (e.g. `kill -9 ` or `poweroff`). In these situtations the workflow does not shutdown cleanly, the process stops abruptly. This means that the scheduler...
When a user closes or navigates away from the WUI the websocket is closed. Currently this results in traceback appearing in the log, we should catch this exception and log...
Authorisation has added to the current (screen) logging of the UI Server. This will get cluttered as more people connect and interact with workflows. We should create a separate logging...
We can make some things configurable via CLI arguments. Add a CLI argument for setting the UI build dir to establish this pattern. See https://github.com/cylc/cylc-uiserver/pull/230#discussion_r679902858 (note there is a pre-existing...
**Describe the bug** @dwsutherland reviewed https://github.com/cylc/cylc-uiserver/pull/124#pullrequestreview-457164367 and his comment raised an interesting point: what happens to the WebSocket connection after the user logs off? The answer is that the WebSocket...
The UIS provides a "status message" for stopped workflows (because there is no scheduler around to do so). Currently this only differentiates between a workflow which has or has not...
The analysis view in the GUI would like access to the memory, CPUs and time that a job requested when it was submitted. This information is presently available via the...
Jupyter Server extension applications may implement a `current_activity` interface. This is used to inform Jupyter Server of any activity with the extension for the purposes of implementing the `shutdown_no_activity_timeout` which...
For scheduler commands, we always log the user who actioned the command (unless they are workflow owner, in which case it is implicit). However, there are some things that are...
