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

Fix database after crash #4

Merged
merged 1 commit into from
Mar 1, 2024
Merged

Fix database after crash #4

merged 1 commit into from
Mar 1, 2024

Conversation

miikasda
Copy link
Owner

@miikasda miikasda commented Mar 1, 2024

If the latest entry in db is "on" when initializing db, it needs to be removed. Otherwise spurious screen on time calculations could happen. This situation can happen for example when OOM killer kills the app.

If the latest entry in db is "on" when initializing db, it needs to
be removed. Otherwise spurious screen on time calculations could happen.
This situation can happen for example when OOM killer kills the app.
@miikasda miikasda merged commit 885f4cc into main Mar 1, 2024
@miikasda miikasda deleted the recover_crash branch March 1, 2024 08:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant