[BR-2319]: feat/add support for configurable SQLite journal mode and enhance entrypoint logging - #690
Merged
Merged
Conversation
…enhance entrypoint logging
|
AlexisMora
approved these changes
Sep 30, 2026
larryrider
approved these changes
Oct 5, 2026
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.



Switches the local SQLite database (the drive item cache) to WAL journal mode, and adds an env var to opt out.
Every CLI command opens this database. In Docker, the keep-alive loop runs
internxt whoamievery 30s while the WebDAV server has the same file open. In the default rollback-journal mode, readers and the writer block each other. WAL lets reads and writes run at the same time.Changes
prepareDatabasesetsjournal_mode = WALandjournal_size_limit = 16MBwhen the connection opens, before TypeORM applies its own pragmas.INXT_SQLITE_JOURNAL_MODE=DELETEswitches back to the rollback journal. It setsDELETEexplicitly, because WAL mode is saved in the database file and a file that's already in WAL would otherwise stay in WAL. Unknown values log a warning and use WAL.memory). We now compare that value and log a warning when it doesn't match. Errors that are thrown (for exampleSQLITE_BUSY) are still logged, not raised.docker/README.mddocuments the new env var.