Repository navigation
Keep the host running when a background service fails - #941
Merged
manuelmayer-dev merged 1 commit intoSep 21, 2026
Merged
Conversation
manuelmayer-dev
deleted the
fix/background-service-crash-stops-host-935
branch
September 21, 2026 15:06
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.
Closes #935
Summary
A failing background service no longer stops the host: the backup scheduler logs the error and retries, and startup services that gate readiness still stop the host explicitly. DatabaseContext opens unpooled connections until Microsoft.Data.Sqlite ships the fix for dotnet/efcore#39008.
Testing
Full solution Release build with warnings as errors and all test suites pass, apart from the Plugin.Cli build test that also fails locally on main. New tests cover the scheduler retry, readiness failures and a throwing background service. Checked in a disposable host with an injected SQLite failure: before, the host stopped; after, it logged the error and the retry created the scheduled backup. The disposed pooled handle itself could not be reproduced on demand.
Checklist