Repository navigation
Close SQLite handles before atomic warehouse replacement - #4
Merged
Merged
Conversation
dev-belly
marked this pull request as ready for review
October 11, 2026 04:15
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
1 participant
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.
The Windows pipeline failed with WinError 32 during warehouse publication because SQLite transaction contexts do not close their connections and pooled readers retain file handles. Explicitly close the check/list connections and use non-pooled SQL readers so a subsequent atomic replacement can complete. Retain rollback behavior for rejected staging builds and add Windows Python 3.12 pipeline/test checks.
Validation: all 465 tests are collected; local Windows passes 464 with the make-help test skipped because make is unavailable. The full ten-step pipeline and all 15 SQL queries pass. Two successive report builds produce identical bytes for ten reports; published reports/charts remain unchanged. Ruff and whitespace checks pass.