Limit autosave #1126
Merged
Limit autosave #1126
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When number of autosaves reaches 60 (2h) the oldest 30 (1h) will be removed
|
Since vistrail files only grow, it is probably only useful to keep one. The previous autosave can be deleted as soon as a new one is done. |
remram44
force-pushed
the
limit_autosave
branch
from
fd82d61
to
af05ca7
Compare
The new one is written before deleting the old one
|
Okay. Now only a single autosave is kept. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Autosaves are generated every 2 minutes and can potentially fill up the disk over time. This patch limits the autosaves to between 30-60 (1-2 h). Is this reasonable?
Ported from UV-CDAT
Should go into v2.2