GitNexus/gitnexus/test/setup.ts
Candido Sales Gomes 5a5850832c
refactor: migrate from KuzuDB to LadybugDB v0.15 (#275)
* refactor: migrate from KuzuDB to LadybugDB v0.15

KuzuDB was archived (Apple acquisition, Oct 2025). LadybugDB is the
community fork with full API compatibility.

- Package swap: kuzu → @ladybugdb/core, kuzu-wasm → @ladybugdb/wasm-core
- Rename all internal paths: kuzu → lbug (adapters, schema, storage)
- Storage path: .gitnexus/kuzu → .gitnexus/lbug (with auto-cleanup)
- Add explicit VECTOR extension loading (required in v0.15)
- Update CI workflow, documentation, and all tests
- 1151 unit + 27 integration tests passing

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* fix: address code review findings (P1-P3)

P1: Fix WASM adapter to use getAll() API, wire cleanupOldKuzuFiles
into analyze command, add symlink path traversal protection.
P2: Cache VECTOR extension load state, batch augmentation engine
queries (20→4), fix web getCopyQuery for multi-language tables,
fix stale KuzuDB references, correct brainstorm package names.
P3: Complete lbug-wasm.d.ts type declarations, batch semantic
search per-label, update stale BM25 comment.

* chore: remove outdated KuzuDB migration brainstorming document

* fix: load FTS extension in MCP pool adapter on init

The read-only pool adapter never loaded the FTS extension, so all
QUERY_FTS_INDEX calls failed silently. This broke search-pool and
augmentation integration tests, and caused empty results in the
web UI server mode.

* feat: implement shared Database caching and connection reference counting

* feat: enhance KuzuDB migration handling and status reporting

* fix: mock cleanupOldKuzuFiles in local backend callTool tests

* fix: update mock for cleanupOldKuzuFiles and adjust imports in callTool tests

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-15 15:53:01 +00:00

29 lines
1.1 KiB
TypeScript

/**
* Vitest per-file setup file (runs inside each forked worker).
*
* Unref's all active handles after each test file so the event loop can
* drain naturally. For non-native test files this is sufficient to let
* the fork exit. For LadybugDB test files, native C++ handles may not expose
* .unref() — CI handles this via process isolation (one vitest invocation
* per LadybugDB test file) so the OS reclaims everything on process exit.
*
* IMPORTANT: We do NOT import lbug-adapter here. Importing it would load
* the native addon even in non-LadybugDB test files, registering persistent
* handles that prevent the fork from exiting.
*
* IMPORTANT: We do NOT call process.exit() here. On Linux, process.exit()
* triggers N-API destructor hooks in the LadybugDB native addon that segfault
* (SIGSEGV), crashing the fork before it can send results back via IPC.
*/
import { afterAll } from 'vitest';
afterAll(() => {
try {
const handles = (process as any)._getActiveHandles?.();
if (handles) {
for (const h of handles) {
if (typeof h.unref === 'function') h.unref();
}
}
} catch {}
});