Skip to content

Conversation

lutter
Copy link
Collaborator

@lutter lutter commented Oct 11, 2025

We have a lot of places where we do blocking database work from a non-blocking tokio task. This PR addresses this longstanding issue by using async database connections and diesel_async. With that, we don't need to rely on error-prone approaches that require spawning blocking tasks whenever we do database work.

Most of this PR is concerned with sprinkling async/await throughout the code base. There are a lot of commits, but most of them are boring, and I tried to structure it so that many of them just add async/await in a few places to make them easy to review individually.

Fixes #905

@lutter lutter force-pushed the lutter/async-store branch 3 times, most recently from 52f8a39 to a8c347b Compare October 12, 2025 13:51
lutter added 26 commits October 17, 2025 18:29
Same for load_deployment and drop_deplyment
@lutter lutter force-pushed the lutter/async-store branch from 662b957 to bd58d19 Compare October 19, 2025 14:41
@lutter lutter force-pushed the lutter/async-store branch from 9099d6c to b132fe7 Compare October 20, 2025 14:12
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.

Move slow db interactions to tokio blocking pool

1 participant