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

Drop worker shared state in shutdown (Sqlite) #1608

Merged
merged 1 commit into from
Jan 4, 2022

Conversation

andrewwhitehead
Copy link
Contributor

@andrewwhitehead andrewwhitehead commented Jan 4, 2022

Related to previous issue #1452

Signed-off-by: Andrew Whitehead <cywolf@gmail.com>
@andrewwhitehead
Copy link
Contributor Author

It would be nice to have a unit test to check this behaviour, but I haven't found a good way to do it yet. Essentially I think it would need to close the database and then immediately try to delete it to show that the close has completed properly, which would probably mean opening a database in the system temp directory (with a known filename). Alternatively I suppose it could check for the presence of a .shm or .wal file after the database is meant to be closed? In any case I've only been able to reproduce the issue on Windows on Github Actions so far.

@abonander abonander merged commit dec0ed1 into launchbadge:master Jan 4, 2022
@andrewwhitehead andrewwhitehead deleted the fix/sqlite-close branch January 6, 2022 18:47
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.

2 participants