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

Add "status" column to dashboard/ls #41

Open
yarikoptic opened this issue Jul 17, 2020 · 2 comments
Open

Add "status" column to dashboard/ls #41

yarikoptic opened this issue Jul 17, 2020 · 2 comments

Comments

@yarikoptic
Copy link
Contributor

yarikoptic commented Jul 17, 2020

ATM I see

$> qme ls
Database: sqlite
1  shell-effb7576-f0da-431f-8e5a-16419753b9aa	bash -c date; sleep 10; date
2  shell-c42c2e0b-ac91-4efd-bc78-4093a9c0c1db	bash -c date; sleep 60; date
3  shell-00d909b6-2119-4e97-8669-449f6786c8bd	bash -c date; sleep 2; date

and

Id | Executor | Name | Command
-- | -- | -- | --
2 | shell | Shell-00d909b6-2119-4e97-8669-449f6786c8bd | bash -c date; sleep 2; date |  
1 | shell | Shell-c42c2e0b-ac91-4efd-bc78-4093a9c0c1db | bash -c date; sleep 60; date |  
0 | shell | Shell-effb7576-f0da-431f-8e5a-16419753b9aa | bash -c date; sleep 10; date

in web ui -- there is no status if the job is still running, has completed ok or not.

@vsoch
Copy link
Owner

vsoch commented Jul 18, 2020

hey @yarikoptic ! You should first be sure that you don't have multiple versions of qme installed - you shouldn't see a version locally that isn't latest if you've installed the latest. For the status, not al executors have a status, so you would need to see this in the executor specific view, e.g.,

image

The front page dashboard can only show what is shared between all executors. Also, the commands are either submit / run and then the client exits. For example, for slurm the command will submit a job, and you can run an action to get a live status. There is no executor that runs some constant ping in the background to look for an updated status, and there is also no executor that submits something in the background and continually looks for a result / error code. I'm not sure how that would be implemented - if you have an idea please take a shot!

@yarikoptic
Copy link
Contributor Author

I would like to see majority (if not all) executes to have (some) status since any job has some, at least submitted, running or completed (successfully or not). It can be executor duty to update it throughout the life cycle of the job in the job record, so that dashboard could display it. And it is the information very useful to have in the dashboard. I will look in the code where/how it could fit in its current form.

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