-
Notifications
You must be signed in to change notification settings - Fork 96
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
Yieldthought/lt persist state #14891
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is awesome! Had one question. Approved
# Restore saved attributes | ||
entry.status = ( | ||
"Cancelled" | ||
if entry_data["status"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should status be "cancelled" if the status is in this list?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes - this is to account for cases in which lt was terminated without its usual shutdown (e.g. ird timeout, connection lost etc). Those processes are gone and are not coming back.
* #0: Tie name of each log to a slot index * #0: Detach log id's from visible index as this changes on deletion * #0: remove logs when deleted from list * #0: Persist lt status in logs/status.json * #0: always reset on error code unless cancelled * #0: Add X to clear all
Ticket
n/a
Problem description
Using lt for multiple runs of the same input would share log files, exiting lt by mistake would lose output and state
What's changed
Unique log index for each run, log files removed when they are removed from lt, lt state persisted between runs
Checklist