refactor JobManager methods for readability
-
spawn -> spawn_once, as it more clearly shows intent.
-
args and kwargs are required to be kwargs, but are optional, meaning tasks that don't need to pass them won't need to pass them.
-
make spawn_once receive a function rather than a coroutine. would let us create future retry logic to this maybe
-
add test for
POST /api/delete_all
as part of refactoring and finding out ways our suite wouldn't catch bugs