Conversation
Collaborator
|
Review requested:
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #66042 +/- ##
==========================================
- Coverage 90.35% 90.35% -0.01%
==========================================
Files 792 792
Lines 275500 275509 +9
Branches 52791 52801 +10
==========================================
+ Hits 248932 248934 +2
Misses 16992 16992
- Partials 9576 9583 +7
🚀 New features to boost your workflow:
|
This comment was marked as outdated.
This comment was marked as outdated.
araujogui
force-pushed
the
sqlite-reopen-state
branch
2 times, most recently
from
September 29, 2026 16:57
f8dd161 to
28b9ebf
Compare
Member
|
Commit body says
How's the SQL |
close() destroys the connection but keeps the DatabaseSync object, and open() did not replay the state held on it. An authorizer set with setAuthorizer() was not reinstalled, silently dropping a deny-all policy. Limits written through db.limits.* reverted to the constructor values. Extension loading was re-enabled from the constructor ceiling rather than the current setting, so the connection flag contradicted a previous enableLoadExtension(false), though loadExtension() itself stayed blocked by its own check. Signed-off-by: Guilherme Araújo <arauujogui@gmail.com> Assisted-by: Claude Code
araujogui
force-pushed
the
sqlite-reopen-state
branch
from
September 30, 2026 12:29
28b9ebf to
25491b3
Compare
Member
Author
It was not, my mistake. Fixed! |
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.
close()destroys the SQLite connection but keeps theDatabaseSyncobject, andOpen()did not replay the state held on that object.Three cases:
db.limits.*went only to the connection, so they reverted to the constructor values.allow_load_extension_(the constructor ceiling) instead ofenable_load_extension_(the current setting), so the connection flag contradicted a previousenableLoadExtension(false). Not exploitable —loadExtension()stays blocked by its own check, and the SQLload_extension()function is never enabled, sinceSQLITE_DBCONFIG_ENABLE_LOAD_EXTENSIONenables only the C API. Fixed for consistency.Fix: re-register the authorizer at the end of
Open(), record runtime limit writes alongside the constructor options so both are replayed, and apply the current load-extension setting rather than the ceiling.