fix archive clean schedule #5480
Merged
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
turns out we were cleaning archive on almost every login, oops. Also, reduce the frequency to once every 30 days, so that 28/29 days a user logs in there is a high chance that the addon never loads, and thus wow only rarely writes to the file.
mrbuds
approved these changes
Oct 17, 2024
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.
turns out we were cleaning archive on almost every login, oops.
Also, reduce the frequency to once every 30 days, so that 28/29 days a user logs in there is a high chance that the addon never loads, and thus wow only rarely writes to the file. This should make it more likely that if the main addon SavedVariables are destroyed by e.g. user running out of disk space, the archive survives intact.