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

Scheduler: add a possibility to cleanup executions after finishing #570

Open
bugy opened this issue Aug 25, 2022 · 4 comments
Open

Scheduler: add a possibility to cleanup executions after finishing #570

bugy opened this issue Aug 25, 2022 · 4 comments

Comments

@bugy
Copy link
Owner

bugy commented Aug 25, 2022

Now, all the scheduled executions stay open, until user sees them.
If a script runs quite often, it causes a lot of tabs, which a user should check, which is not very UX friendly
Also, this consumes server resources (mostly memory)
So there should be an option to mark the execution as viewed automatically

I would make it default behavior, because a user can always see execution log via history.
Except the cases, when there is an output file

@bugy bugy added the feature label Aug 25, 2022
@bugy bugy changed the title Scheduler: add a possibility to cleanup executions additionally Scheduler: add a possibility to cleanup executions after finishing Aug 26, 2022
@bugy
Copy link
Owner Author

bugy commented Aug 26, 2022

Done. Now scheduled executions are cleaned up (i.e. removed from active executions) automatically by default. This behaviour can be disabled via scheduling.auto_cleanup = false setting in a script configuration

CC @barrelltitor this should be available on dev version

@bugy bugy added this to the 1.18.0 milestone Aug 26, 2022
@bugy
Copy link
Owner Author

bugy commented Aug 26, 2022

@barrelltitor
Copy link

It looks like I missed out on this amazing update. I'm away for the moment, but I will test this as soon as I can!

@barrelltitor
Copy link

It is working great so far! Thank you!

@bugy bugy added the resolved label Jan 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants