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

Live command output #43

Open
aristosv opened this issue Feb 5, 2022 · 6 comments
Open

Live command output #43

aristosv opened this issue Feb 5, 2022 · 6 comments
Labels
type: feature-request New feature request

Comments

@aristosv
Copy link

aristosv commented Feb 5, 2022

What seems to be the problem?!
Is there a way to show a more prominent output when a button is pressed?
I realise I can go to Logs > stderr, or Logs > stdout, but it would be nice if I could see an output of the command as soon as I press a button. Perhaps a popup, or a side menu, showing what is going on with the command I just executed.

A good example is rundeck. It shows in real time the output of the command, a kill button and a progress bar. I realise of course this is a young project. These are just suggestions for future features.

Greenshot 2022-02-05 17 47 53

What package/file/container did you use to install OliveTin?
OliveTin_2022-01-06_linux_arm64.deb

@jamesread
Copy link
Collaborator

Hey @aristosv , indeed, this is quite a commonly requested feature - a "popup" once done / to view progress.

At the moment, OliveTin only gets logs once the command exits (or times out and is killed). I'll have to look into doing something like log streaming to make this meaningful.

I'll accept this feature request, but it might take a little while to get this one implemented.

@l20f111164
Copy link

We strongly recommend supporting this feature, which would be perfect if implemented.

@jamesread
Copy link
Collaborator

Hey, I've just had some time to work on this, and wanted to share a development video that calls out some relevant changes. Does this look like it's going in the right direction?

https://youtu.be/vWAD04Wpa8U

@FieldofClay
Copy link

Those features are a step in the right direction for my use case. It is great to have stdout popup to see the output of the command. Adding streaming stdout would be the final piece, so you could for example, see which task in the playbook is currently running.

I think a progress bar is a step too far, you'd need to time previous runs to guess or somehow pull it from the command (if it outputs an easily captured %). Not worth the effort and goes beyond the simplicity of the project.

@jamesread
Copy link
Collaborator

e641e9a contains early support for killing commands. :-) Work in progress.

@jamesread
Copy link
Collaborator

I need to break this issue down into it's constituent parts - I've just added kill support which will make the next release very shortly, so I'm going to remove "kill button" from the issue title. I'm also going to drop the progress bar support into a new issue, and name it more like "estimated time". This would need log support and a few other things.

Therefore this issue will be used to track "Live command output" - which is what a lot of people would like to see.

@jamesread jamesread changed the title live command output, kill button & progress bar Live command output Apr 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature-request New feature request
Development

No branches or pull requests

4 participants