Repository navigation
Fix leaked milestone queries and expand core C API coverage - #412
Merged
Merged
Conversation
10 tasks done
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.
Description
Milestone readers leaked their outer SQLite statement when loading a milestone's dates threw. This can keep a failed query and its database connection alive. Give all four readers scoped statement ownership so their queries are finalized on success and exceptions. A regression test reproduced one leaked statement before the fix and now verifies cleanup for card, epoch-range, instant-range and calendar-day reads.
Expand core coverage through the generated C API, checking returned records and persisted behavior: history and restore, atomic recovery rejection, encrypted snapshots and missing keys, private storage bindings, project ordering, card placement, search, Trash, local Git sync, remote failures, signing callbacks and database reports. Milestone write-failure tests also verify that the caller's transaction preserves the original data.
The only production-code change is the milestone statement cleanup. No new coverage exclusions or dependencies are introduced.
Validation
./make.sh coverage: 821/821 tests passed; HTML and JSON reports generated successfully.git diff --checkpassed.Contribution Checklist
Licensing
Code Quality
Security & Dependencies
Documentation