feat: add supervised background workers#138
Open
ItayTheDar wants to merge 1 commit into
Open
Conversation
ItayTheDar
marked this pull request as ready for review
July 25, 2026 19:45
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
BackgroundWorkerand fixed-delayIntervalWorkerAPIsWorkerHostsupervision with restart policies, capped exponential backoff, status reporting, cooperative shutdown, and forced cancellation after a grace timeoutWorkerAppFactoryandrun_workers()support with SIGTERM/SIGINT handlingWhy
Creating long-lived asyncio tasks during the existing synchronous factory bootstrap can bind them to a temporary event loop that is closed immediately afterward. This feature gives background work a first-class runtime that creates tasks on the serving loop, while preserving normal PyNest dependency injection and lifecycle ordering.
Developer impact
Workers are registered as normal module providers and can use constructor injection. HTTP applications require no extra startup code, while dedicated worker processes can run without FastAPI. Recurring jobs can use
IntervalWorker; cron/calendar semantics remain intentionally outside core because they require explicit timezone, persistence, misfire, and distributed-locking policies.Validation
uv run pytest -q— 201 passeduv run --group docs mkdocs build --strict— passedgit diff --check— passed