Skip to content

Conversation

@dwsutherland
Copy link
Member

@dwsutherland dwsutherland commented Nov 13, 2025

While managing ESNZ/NIWA's operation, It's always bugged me that I have to go elsewhere (top of workflow log or cylc scan command or table view) to find out which host this workflow is running on..
So I though it would be useful to have it in the toolbar of the workflow workspace view (as it is for Cylc version, which now only shows if it differs from UIS cylc-flow version):
cylc-ui-toolbar-info-icon-vpopup

Check List

  • I have read CONTRIBUTING.md and added my name as a Code Contributor.
  • Contains logically grouped changes (else tidy your branch by rebase).
  • Does not contain off-topic changes (use other PRs for other changes).
  • Applied any dependency changes to both setup.cfg (and conda-environment.yml if present).
  • Tests are included (or explain why tests are not needed).
  • Changelog entry included if this is a change that can affect users
  • Cylc-Doc pull request opened if required at cylc/cylc-doc/pull/XXXX.
  • If this is a bug fix, PR should be raised against the relevant ?.?.x branch.

@dwsutherland dwsutherland self-assigned this Nov 13, 2025
@MetRonnie MetRonnie self-requested a review November 13, 2025 09:47
@oliver-sanders
Copy link
Member

Makes sense. But, adding this to the workflow status does make it rather long. Our operators seem to be keen on having lots of narrow windows side-by-side where this information would be cut off.


We do intend to extend the "Info View" to also provide workflow information, including metadata and the hostname, etc - #1898

Would this satisfy your requirements? Or would opening a new view be too inconvenient?


Otherwise, would you be ok with making this information available via a tooltip?

E.g, we could have an information icon next to the workflow ID. Hover over it to reveal the hostname, port, etc (all the information from the workflows table). Click on it to bring up the "Info View" for the workflow (along with metadata, broadcasts, etc).

WDYT?

@dwsutherland
Copy link
Member Author

dwsutherland commented Nov 14, 2025

We do intend to extend the "Info View". . .
Would this satisfy your requirements? Or would opening a new view be too inconvenient?

e.g, we could have an information icon next to the workflow ID

All of the above really, workflow info view with more information than the icon hover (maybe a lumino tab opened on clicking on the icon)..

Perhaps close this on the open/merge of that PR...
Or if that is a longer term thing, get this into a maintenance release? (it's a fairly simple change)

adding this to the workflow status does make it rather long

To be fair, some server/user combinations can be very long... (although most workflow status messages are just running/paused ... not Running to stop at 20200101T0000Z)

@oliver-sanders
Copy link
Member

oliver-sanders commented Nov 19, 2025

I hadn't twigged (or more likely had forgotten) that we already do this with the Cylc version. That should really get lumped in with this.

All of the above really

Ok, we can easily add the hover-over icon now, should be a simple change.

Here's a starter for 10:

<v-tooltip>
  <template v-slot:activator="{ props }">
    <v-icon icon="mdi-information-outline" v-bind="props" />
  </template>
  <dl>
    <dt>Owner</dt>
    <dd>{{ currentWorkflow.node.owner }}</dd>
    <dt>Host</dt>
    <dd>{ currentWorkflow.node.host }}</dd>
    <dt>Cylc version</dt>
    <dd>...</dd>
  </dl> 
</v-tooltip>

Should be able to stick that next to the workflow ID in the toolbar.

@dwsutherland dwsutherland force-pushed the host-in-workflow-banner branch from 7e47674 to 23669e5 Compare November 20, 2025 04:28
@dwsutherland
Copy link
Member Author

dwsutherland commented Nov 20, 2025

Ok, I've made an attempt at adding the info icon hover:
image
(I've kept the Cylc version on the toolbar, however, it is redundant if people don't want it at a glance)

I've set it to only show when the workflow is running, but can change that (if we want to include info that's relevant when not running):
image

@dwsutherland dwsutherland force-pushed the host-in-workflow-banner branch from d689227 to 67ca97f Compare November 20, 2025 08:15
@dwsutherland dwsutherland changed the title add owner@host to workspace toolbar add info icon with hover details to workspace toolbar Nov 23, 2025
Copy link
Member

@MetRonnie MetRonnie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Preferably this icon would be to the right of the fixed controls, so that those controls do not jump when the workflow starts/stops.

Also IMO the tooltip would be easier to read if the fields were on the same line as their title, i.e.

Owner: j.bloggs

instead of

Owner:
j.bloggs

Will try to get this into 2.11.0 but for now I've tagged it against 2.12.0

@MetRonnie MetRonnie added this to the 2.12.0 milestone Nov 24, 2025
@dwsutherland dwsutherland force-pushed the host-in-workflow-banner branch from 67ca97f to 4248d58 Compare November 25, 2025 05:09
@dwsutherland
Copy link
Member Author

dwsutherland commented Nov 25, 2025

Preferably this icon would be to the right of the fixed controls, so that those controls do not jump when the workflow starts/stops.

Also IMO the tooltip would be easier to read if the fields were on the same line as their title, i.e.

Done. I also boldened the item names, removed the version next to status (as it's redundant being so close) and fixed a hover-over issue (where anywhere in the toolbar would activate it):
image

@dwsutherland dwsutherland force-pushed the host-in-workflow-banner branch from 4248d58 to 7d94d7c Compare November 25, 2025 05:17
@MetRonnie
Copy link
Member

Nice, however I think it is useful to see the Cylc version at a glance in case it's an older version. So I propose using a chip with the icon and version: dwsutherland#73

WDYT?

@oliver-sanders
Copy link
Member

Personally, I don't think that the Cylc version should be visible in the toolbar.

There's much too much information about a workflow to display in this manner, and the Cylc version isn't generally pertinent.

The versions of all workflows are visible in the "Workflow Table" view. Also, we will one day provide an upgrade functionality which will be accessible via the workflows sidebar.

@MetRonnie
Copy link
Member

Also, we will one day provide an upgrade functionality which will be accessible via the workflows sidebar.

Happy for it to go away into the tooltip when we reach that point. However for the time being I think it's useful for Ops here

@dwsutherland
Copy link
Member Author

dwsutherland commented Nov 26, 2025

Also, we will one day provide an upgrade functionality which will be accessible via the workflows sidebar.

Happy for it to go away into the tooltip when we reach that point. However for the time being I think it's useful for Ops here

It is useful for Ops here (about as useful as knowing the host IMO)..

If the UIS version is at hand (which it is), it could pop-up/show if different... Thoughts?

@dwsutherland
Copy link
Member Author

dwsutherland commented Nov 26, 2025

If the UIS version is at hand (which it is), it could pop-up/show if different... Thoughts?

Here it is:
image

(not sure how the status message isn't bold, but the version is... wasn't when combined, if I have to combine again I will)

@dwsutherland dwsutherland force-pushed the host-in-workflow-banner branch from 48c38c9 to 38ca379 Compare November 26, 2025 09:33
@dwsutherland
Copy link
Member Author

Ok, I've fixed the use of inject and surrounding code, and also tidied up style..
Feels like it's responding properly, and looks better now:
cylc-ui-toolbar-info-icon-vpopup

@dwsutherland dwsutherland force-pushed the host-in-workflow-banner branch from acd5f28 to 8f02b5d Compare November 27, 2025 01:02
Copy link
Member

@MetRonnie MetRonnie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants