* fix(deps): upgrade @ladybugdb/core to 0.16.0 to resolve native segfaults
Resolves the SIGSEGV / access-violation (0xC0000005) / exit-139 crashes that
have been reported widely since 1.6.3. The native crashes originate in
@ladybugdb/core 0.15.x — primarily during FTS index creation, VECTOR
extension load, and concurrent query teardown — and are reproducible on
Linux, macOS and Windows. The maintainer-confirmed fix is to bump the
runtime to 0.16.0, which ships nodejs async + memory-management fixes,
extension ABI bump, and macOS Intel binaries.
Adopting 0.16.0 cleanly required three supporting changes; without them
the upgrade itself regresses other paths:
1. maxDBSize must be passed explicitly. 0.16.0 keeps the upstream JSDoc
note that the default 0 is "introduced temporarily for now to get
around with the default 8 TB mmap address space limit some
environment". Constrained CI runners and laptops cannot reserve 8 TB
and crash with "Buffer manager exception: Mmap for size
8796093022208 failed." A new gitnexus/src/core/lbug/lbug-config.ts
centralises a 16 GiB default (overridable via
GITNEXUS_LBUG_MAX_DB_SIZE) and every Database() construction site
now passes it.
2. enableCompression default flipped from false to true in 0.16.0. Every
Database() call site is updated to pass false explicitly so existing
GitNexus indexes keep the same wire format.
3. Bridge DB sidecar files (.wal, .shadow). 0.16.0 enforces a database-id
check on .wal / .shadow sidecars and rejects opens whose sidecars
belong to a different base name. writeBridge now (a) cleans the full
sidecar set when removing the tmp slot, (b) renames .wal / .shadow
alongside the main file during the atomic .tmp -> .lbug swap, and
(c) wraps openBridgeDbReadOnly in a bounded retry on transient
Win32-Error-33 lock errors. Eager db.init() / conn.init() forces the
lazy native handle to surface lock contention at the retry site.
Known limitation (not a regression): on Windows the 0.16.0 native binary
does not release the OS file lock until the process exits, so the
close-then-reopen-same-process pattern raises Error 33 after the first
close. Production paths (analyze / serve / mcp each open the DB exactly
once per process) are unaffected, but eight tests that exercise the
pattern are guarded with a process.platform === 'win32' skip; CI's
Linux + macOS shards exercise them as before. Tracking upstream:
kuzudb/kuzu#3872 / #3883 / #4730.
Closes#1136#1154#1160#1162#1178#1195#1196#1199#1204#1206
Refs #1209 (supersedes — Dependabot bump without the supporting fixes)
Made-with: Cursor
* fix(test): isolate LadybugDB native test state
Use per-suite LadybugDB databases in integration helpers so test forks do not reopen a database created by Vitest global setup, and centralize Windows-tolerant native temp cleanup for bridge tests.
* fix(lbug): avoid bridge existence reopen
Reuse the built LadybugDB config in the extension installer and avoid native close/reopen cycles when checking bridge existence on Windows.
Made-with: Cursor
* chore(docs): exclude local lbug plan
Keep the refactor planning note out of the PR while leaving the ignored local copy on disk.
Made-with: Cursor
* refactor(lbug): centralize database construction
Route LadybugDB opens through shared helpers so native constructor defaults stay consistent across core, pool, bridge, and extension install paths.
Made-with: Cursor
---------
Co-authored-by: magyargergo <11230420+magyargergo@users.noreply.github.com>
