Dockery/Trilium
1
0
Fork 0
mirror of https://github.com/zadam/trilium.git synced 2026-05-07 11:17:01 +02:00
Code Issues Packages Projects Releases Activity

fix(server): share tests no longer working

Browse Source
This commit is contained in:
Elian Doran
2026-04-09 17:46:09 +03:00
parent f40de0a017
commit 6e0e7847e4
1 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
apps/server/src/share/sql.ts
View File

@@ -10,16 +10,16 @@ let dbConnectionReady = false;
sql_init.dbReady.then(() => {
// The share module opens its own read-only connection to the on-disk
// database for isolation from the main read/write connection. In
// integration test mode the database is in-memory (loaded from a
// fixture buffer) and no file exists on disk, so opening one would
// throw SQLITE_CANTOPEN. Tests that exercise share functionality
// would need a different approach; skipping here keeps unrelated
// test files from failing on an unhandled rejection.
if (process.env.TRILIUM_INTEGRATION_TEST) {
return;
}
// integration test mode `dataDir.DOCUMENT_PATH` doesn't contain a real
// database (the main connection is in-memory, loaded from a fixture
// buffer), so we open the fixture file directly from its new location
// in core. The share connection still gets its own independent
// read-only handle, matching production semantics.
const dbPath = process.env.TRILIUM_INTEGRATION_TEST
? require.resolve("@triliumnext/core/src/test/fixtures/document.db")
: dataDir.DOCUMENT_PATH;
dbConnection = new Database(dataDir.DOCUMENT_PATH, {
dbConnection = new Database(dbPath, {
readonly: true,
nativeBinding: process.env.BETTERSQLITE3_NATIVE_PATH || undefined
});