Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A way to determine the open Log without selecting it #2023

Open
ColemanTom opened this issue Dec 9, 2024 · 1 comment
Open

A way to determine the open Log without selecting it #2023

ColemanTom opened this issue Dec 9, 2024 · 1 comment

Comments

@ColemanTom
Copy link

Problem

If you have a workflow open in the WUI and have a couple of logs opened, without selecting them you can't tell which log it is for.

image

You wouldn't know by looking that the first is currently showing the scheduler log and the second a task log

Proposed Solution

  • More precise naming of what log is opened
    • would have to update if someone changes what is displayed
    • For long task ids, it could be a bit much
  • Hover text?
  • Some other thing that UX people would be able to suggest
@oliver-sanders
Copy link
Member

The biggest problem here is somehow summarizing the cycle point, task name and job submission number into something concise enough to fit into the tab title without making the UI clunky.

Text editors have been dealing with this sort of problem for a while now, e.g, take a look at the different configuration options in this Vim plugin: https://github.com/vim-airline/vim-airline?tab=readme-ov-file#default

We could potentially pick one of those methods, however, the text would still end up lengthy.

E.g, job IDs could be shortened like so:

20000101T0000Z/long_task_name_foo_bar_baz/01  ->  2000../l/01
20010101T0000Z/long_task_name_foo_bar_baz/02  ->  2001../l/02

But we would need a global inventory of all open log tabs to be able to shorten these appreciably.

Perhaps the easiest way forward is just to include the filename in the tab name (e.g. job.out or 01-scheduler-01.log)?

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

No branches or pull requests

2 participants