mirror of
https://github.com/abhigyanpatwari/GitNexus.git
synced 2026-10-01 02:01:24 +00:00
* fix(lbug): pin Ladybug core so Dependabot cannot ship a skewed FTS artifact The extension version is a separate upstream constant. Ignore daily core bumps and fail the pairing gate when the committed manifest does not name the installed core. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(lbug): make doctor and CI FTS gates resolve the packaged artifact Doctor and the REQUIRE_FTS file gates still treated an empty ~/.lbdb as unavailable, which would turn three CI jobs red once analyze stops installing into that tree. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(lbug): name native-abort and tuple-missing so analyze cannot mis-advise The CLI summary's trailing else treated every unknown skip reason as a missing extension. New crash and platform causes must get their own remedies, not a network-install hint. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(lbug): delete the dead read-path FTS index create ensureFTSIndex had no production callers and swallowed read-only CREATE_FTS_INDEX failures, which hid the only signal that a reader tried to write. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(lbug): vendor per-platform FTS artifacts so analyze needs no host install Keyword search depended on a CDN fetch into ~/.lbdb. Shipping the five published tuples inside the package makes air-gapped and ignore-scripts installs load the same artifact the publish gate checksums. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(lbug): load the packaged FTS artifact before any network install Analyze still required a CDN fetch into ~/.lbdb even when the package already shipped the file. FTS now path-loads the vendored tuple first and records source labels so a later truncated home copy cannot steal the diagnosis. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(lbug): diagnose a core/extension version skew instead of a missing runtime A structurally valid FTS artifact whose path version disagrees with the packaged pin must name both versions, not prescribe VC++ or OpenSSL. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(lbug): stamp an FTS phase so repair stays usable after an in-place abort A native CREATE_FTS_INDEX abort leaves no skip reason; the next run infers it from the dirty flag, and --repair-fts must not treat that phase as a half-written graph. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(lbug): park an in-place FTS crash WAL without wiping the graph An FTS abort after a successful checkpoint must reopen the live index on macOS, Windows, and Linux. Staging never parks the live WAL; readers keep today's large-WAL refusal. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(lbug): refuse read-only opens of an FTS-poisoned WAL MCP and serve cannot repair a leftover in-place abort. Fail before the native open and name --repair-fts, on macOS, Windows, and Linux. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(lbug): name a vendor-neutral Windows OpenSSL prerequisite OQ1 is unanswered here so GitNexus does not ship OpenSSL DLLs. Windows FTS now asks for a system OpenSSL 3 runtime instead of Git Bash PATH. Co-authored-by: Cursor <cursoragent@cursor.com> * test(lbug): inject the FTS vendor root and redact it on HTTP and MCP Path-loaded artifacts no longer vary with HOME. Tests pass an injected vendor tree and assert search warnings never leak a filesystem path. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(lbug): document load-only as the global FTS install default Analyze still overrides to auto. Packaged per-platform artifacts load before any network install on macOS, Windows, and Linux. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(lbug): format the FTS install-policy README table Prettier does not run on Markdown in pre-commit, so the U10 table wrap needs its own formatting commit. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(lbug): skip FTS CREATE after a persisted native abort A recovered analyze run was retrying CREATE_FTS_INDEX from skipReason alone. Keep that skip until --repair-fts, fail closed on unsupported tuples, and honor the checkpoint warrant for park/repair. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(lbug): honor checkpoint flushed warrant and align FTS tests with packaged vendor A no-op CHECKPOINT must not satisfy the FTS park warrant, and CI still asserted HOME-only FTS isolation after analyze started path-LOADing the packaged artifact. Co-authored-by: Cursor <cursoragent@cursor.com> * test(lbug): accept a nonempty incremental write set in the #2790 recovery check FTS-phase recovery can incremental-add files (changed=0, added=1). That is not the #2790 empty-diff wipe skip. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(lbug): compare FTS home versions to the core pin and tighten the publish filename gate Ladybug's ~/.lbdb/extension directory is the runtime/core version; treating it as the artifact version false-diagnosed skew. The publish guard now rejects a path-escaping filename the same way the fetch script does. Co-authored-by: Cursor <cursoragent@cursor.com> * test(lbug): seed FTS e2e fixtures from the packaged vendor artifact A machine with no ~/.lbdb copy should still run the vendor-survivorship cases; the seed no longer depends on HOME or a network install. Co-authored-by: Cursor <cursoragent@cursor.com> * Address PR review feedback (#3274) Keep in-place FTS abort evidence after persist so a second CREATE abort cannot fail-open readers, and close the CLI, loader, embed, and e2e gaps the review called out. Note: full npm test hit Ladybug worker-pool startup failures under memory pressure; tsc and 180 targeted unit tests passed. Co-authored-by: Cursor <cursoragent@cursor.com> * Address PR review feedback (#3274) Run the vendored-path symlink guard on the OS matrix, put e2e HOME fixtures on Ladybug's real extension layout, pin the embed crash-WAL gate before the writable open, and let analyze writers park through missing-shadow recovery. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(lbug): keep --repair-fts CI green after vendored-first FTS Never-installed warning fixtures must not inspect a packaged vendor binary, and a failed dirty restamp must not abort an otherwise successful --repair-fts run. Co-authored-by: Cursor <cursoragent@cursor.com> * test(cli): give the #1169 analyze e2e the same 90s Windows budget as its sibling The first #1169 persist-meta case was still on a 60s spawn/it budget and was killed banner-only on windows-latest after the FTS warning fixture no longer failed the shard first. Co-authored-by: Cursor <cursoragent@cursor.com> * test(ci): reweight Windows shards after the FTS e2e grew Vendored-first HOME fixtures pushed fts-extension-e2e to ~6 minutes on windows-latest, so the old 146s weight packed it with skills-e2e and blew the 20-minute watchdog. Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Gergo Magyar <gergomagyar0@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
98 lines
4.2 KiB
TypeScript
98 lines
4.2 KiB
TypeScript
/**
|
|
* Regression Tests: read-only DB error discriminator (#1224)
|
|
*
|
|
* The MCP query pool opens LadybugDB read-only. A write there surfaces
|
|
* "Cannot execute write operations in a read-only database". The
|
|
* discriminator must stay precise so lock / busy / "already exists"
|
|
* errors are not swallowed.
|
|
*
|
|
* This file unit-tests the discriminator directly so future refactors
|
|
* keep the contract.
|
|
*/
|
|
import { readFileSync } from 'node:fs';
|
|
import path from 'node:path';
|
|
import { fileURLToPath } from 'node:url';
|
|
import { describe, it, expect } from 'vitest';
|
|
import { isReadOnlyDbError } from '../../src/core/lbug/lbug-adapter.js';
|
|
|
|
const adapterSource = readFileSync(
|
|
path.join(path.dirname(fileURLToPath(import.meta.url)), '../../src/core/lbug/lbug-adapter.ts'),
|
|
'utf8',
|
|
);
|
|
|
|
describe('isReadOnlyDbError', () => {
|
|
it('matches the canonical LadybugDB read-only message verbatim', () => {
|
|
const err = new Error(
|
|
'Connection exception: Cannot execute write operations in a read-only database!',
|
|
);
|
|
expect(isReadOnlyDbError(err)).toBe(true);
|
|
});
|
|
|
|
it('matches when the error is wrapped in additional prefix text', () => {
|
|
const err = new Error(
|
|
'Runtime exception: Cannot execute write operations in a read-only database',
|
|
);
|
|
expect(isReadOnlyDbError(err)).toBe(true);
|
|
});
|
|
|
|
it('is case-insensitive on the "read-only" substring', () => {
|
|
expect(isReadOnlyDbError(new Error('Read-Only Database access denied'))).toBe(true);
|
|
});
|
|
|
|
it('accepts non-Error values (string, unknown) without throwing', () => {
|
|
expect(isReadOnlyDbError('write rejected: read-only database')).toBe(true);
|
|
expect(isReadOnlyDbError({ toString: () => 'read-only database' })).toBe(true);
|
|
expect(isReadOnlyDbError(null)).toBe(false);
|
|
expect(isReadOnlyDbError(undefined)).toBe(false);
|
|
});
|
|
|
|
it('detects a read-only error wrapped as a `cause` (#2068 — pool-adapter wrapper)', () => {
|
|
// The pool adapter rethrows native read-only failures as a friendly
|
|
// message with the original error preserved on `cause`. Detection must see
|
|
// through the wrapper so the MCP/HTTP handlers surface their curated message.
|
|
const wrapped = new Error('Write operations are not allowed. The pool adapter is read-only.', {
|
|
cause: new Error('Cannot execute write operations in a read-only database!'),
|
|
});
|
|
expect(isReadOnlyDbError(wrapped)).toBe(true);
|
|
});
|
|
|
|
it('does NOT match a wrapper whose cause chain is unrelated', () => {
|
|
const wrapped = new Error('Query failed', { cause: new Error('Connection refused') });
|
|
expect(isReadOnlyDbError(wrapped)).toBe(false);
|
|
});
|
|
|
|
it('terminates on a cyclic cause chain without hanging', () => {
|
|
const a = new Error('boom a') as Error & { cause?: unknown };
|
|
const b = new Error('boom b') as Error & { cause?: unknown };
|
|
a.cause = b;
|
|
b.cause = a;
|
|
expect(isReadOnlyDbError(a)).toBe(false);
|
|
});
|
|
|
|
it('stops cleanly on a non-Error cause', () => {
|
|
const wrapped = new Error('outer', { cause: 'just a string' });
|
|
expect(isReadOnlyDbError(wrapped)).toBe(false);
|
|
});
|
|
|
|
it('does NOT match unrelated errors that create/drop must still surface', () => {
|
|
// Lock contention — handled separately by isDbBusyError; must not be
|
|
// silenced by the read-only filter.
|
|
expect(isReadOnlyDbError(new Error('Could not set lock on file'))).toBe(false);
|
|
// "already exists" — the happy idempotent path inside createFTSIndex.
|
|
expect(isReadOnlyDbError(new Error('Index file_fts already exists'))).toBe(false);
|
|
// Schema-level problem.
|
|
expect(isReadOnlyDbError(new Error('Table File does not exist'))).toBe(false);
|
|
// Generic transient error.
|
|
expect(isReadOnlyDbError(new Error('Connection refused'))).toBe(false);
|
|
});
|
|
|
|
it('has no production ensureFTSIndex residue (#1500)', () => {
|
|
expect(adapterSource).not.toContain('ensureFTSIndex');
|
|
expect(adapterSource).toContain('export const createFTSIndex');
|
|
const start = adapterSource.indexOf('export const createFTSIndex');
|
|
const nextExport = adapterSource.indexOf('\nexport const', start + 1);
|
|
const createBody = adapterSource.slice(start, nextExport);
|
|
expect(createBody).toContain("includes('already exists')");
|
|
expect(createBody).not.toContain('isReadOnlyDbError');
|
|
});
|
|
});
|