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(db): Fix db.threadsafe #212

Merged
merged 1 commit into from
Nov 7, 2024
Merged

fix(db): Fix db.threadsafe #212

merged 1 commit into from
Nov 7, 2024

Conversation

ketiltrout
Copy link
Member

@ketiltrout ketiltrout commented Nov 6, 2024

Something I found while testing #210:

If we want db._base.threadsafe to be imported into __init__, it can't be a scalar (because it's going to change after the import).

Instead, make it a function.

Bonus: no need to try to import subprocess every time a command is run. Just import it once at module import.

If we want db._base.threadsafe to be imported into __init__, it
can't be a scalar (because it's going to change after the import).

Instead, make it a function.

Bonus: no need to try to import `subprocess` every time a command
is run.  Just import it once at module import.
@ketiltrout ketiltrout merged commit 1d17a46 into master Nov 7, 2024
3 checks passed
@ketiltrout ketiltrout deleted the fix_threadsafe branch November 7, 2024 03:21
@ketiltrout
Copy link
Member Author

This is running on cedar already as part of the dirty clone I'm using to test #210 . I'm going to leave it there as-is and rebase back to master once #210 is tested and debugged and merged.

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