mirror of
https://github.com/abhigyanpatwari/GitNexus.git
synced 2026-08-28 05:25:25 +00:00
Some checks are pending
CodeQL / Analyze (javascript-typescript) (push) Waiting to run
CodeQL / Analyze (python) (push) Waiting to run
Gitleaks / gitleaks (push) Waiting to run
Publish / Classify release event (push) Waiting to run
Publish / RC guard (marker + release-PR skip) (push) Blocked by required conditions
Publish / ci (push) Blocked by required conditions
Publish / Publish to npm (push) Blocked by required conditions
Publish / Build & Push RC Docker images (push) Blocked by required conditions
Scorecard / Scorecard analysis (push) Waiting to run
Trivy Image Scan / Trivy (gitnexus-cli) (push) Waiting to run
Trivy Image Scan / Trivy (gitnexus-web) (push) Waiting to run
* feat(lbug): classify FTS extension load errors with Windows missing-dependency guard (#2374) Add classifyExtensionLoadError() — a pure-string, lbug-free four-way classifier (missing_file / corrupt_file / missing_dependency / unknown). The Windows catch-all guard keys missing_dependency strictly on the error-126 signal, never LadybugDB's generic 'Failed to load library … needed by extension' wrapper, so 127/5/1114 and truncated (193) files route correctly. * feat(fts): surface classified missing-dependency remedy in doctor, repair-fts, and degrade warnings (#2374) Route the FTS load reason through classifyExtensionLoadError at all four surfaces (doctor, --repair-fts error, analyze degrade log, ftsDegradedWarning). For the Windows missing-dependency class, emit the runtime-install remedy (VC++ redist, then OpenSSL) instead of the wrong reinstall-over-network guidance; other classes keep their existing routing. Path redaction preserved on the client-facing warning. * test(fts): assert doctor surfaces the classified remedy end-to-end (#2374) Extend the broken-file e2e: doctor now prints the corrupt-file re-download remedy through the real CLI, and the Windows missing-dependency remedy (VC++/OpenSSL) must not misfire on a corrupt file — the catch-all guard, verified end-to-end. Also assert the repair path does not misfire. * style(fts): apply prettier formatting to #2374 diagnosis files * feat(fts): language-independent hedged fallback for Windows load failures (#2374) The Windows OS-error tail is localized, so matching only en/zh 126 text left other locales on the generic 'run doctor' remedy. lbug's 'Failed to load library' wrapper is English on every platform and present for all load failures, so use it as a fallback: when the localized tail matches no specific class, emit a hedged remedy that points the user at their own OS error and offers both branches (install runtime / --repair-fts) without prescribing the wrong single fix. Precise en/zh 126 keeps its definite remedy. * feat(fts): language-independent structural classifier via binary inspection (#2374) Add diagnoseExtensionLoad: pull the extension's file path out of lbug's own English wrapper and inspect the binary header (PE/ELF/Mach-O magic + arch) directly, so corrupt-vs-valid is decided by the file itself, not the localized OS-error tail. A valid binary that still failed to load ⇒ missing_dependency (runtime dep), decided in any OS display language and on all three platforms. Falls back to the string classifier (with its hedged fallback) when the file can't be read. Wire all four surfaces to it. Event Viewer / GetLastError-via-FFI were dead ends (lbug catches the failure — no crash event; no native FFI dep). * test(fts): exercise the structural classifier on real binaries (#2374) Add an integration suite that runs inspectExtensionBinary/diagnoseExtensionLoad against genuine binaries — the running node executable, the real lbugjs.node addon, and the installed FTS extension (valid); a truncated real binary and a real text file (corrupt). Registered in cross-platform-tests PLATFORM_LOGIC so it runs on the Windows + macOS matrix, proving the PE and Mach-O header parsing on real PE/Mach-O files (ubuntu covers ELF). * fix(fts): honor a corrupt_file verdict over a structurally-valid header (#2374) The structural probe in diagnoseExtensionLoad inspects only the first 4 KB, so a download truncated after its header reads 'valid' and was routed to the "install VC++, reinstalling will NOT help" remedy — the exact loop #2374 exists to kill, for the truncated-download case the module docstring claims it handles. Honor the loader's own corruption report ("file too short" / Windows error 193 "not a valid Win32 application") before defaulting to the dependency remedy; localized corrupt tails stay hedged missing_dependency, preserving language-independence. Addresses PR #2383 review finding F1. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(fts): return indeterminate for a PE header beyond the read window (#2374) The structural probe reads only BINARY_HEADER_BYTES (4 KB). A valid PE with a large DOS stub whose e_lfanew points past that window was wrongly called 'corrupt', routing a fine DLL to "re-download". A garbage e_lfanew from a truly corrupt file is indistinguishable from here, so widen the header verdict with 'indeterminate' and return it in that case; the caller then defers to the loader's own report instead of asserting a false verdict. Fat Mach-O stays valid (LadybugDB ships thin per-arch binaries). Also covers the unmapped-arch and garbage-PE-signature branches. Addresses PR #2383 review finding F1-secondary. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(fts): drop contradictory reinstall guidance from the analyze degrade log (#2374) For a missing runtime dependency the extension file is present, so appending FTS_UNAVAILABLE_MESSAGE (which tells the user to install it "with network access") to the remedy ("reinstalling will NOT help") produced self-contradictory guidance on the main analyze surface. Lead the missing_dependency degrade log with the class-neutral sentence (FTS_UNAVAILABLE_LEAD) and append only the classified remedy; other classes keep FTS_UNAVAILABLE_MESSAGE unchanged. Addresses PR #2383 review finding F2. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * perf(fts): cache the load diagnosis so the degraded warning does no per-request I/O (#2374) ftsDegradedWarning() runs on every degraded /api/search response and MCP query, and it was calling diagnoseExtensionLoad — a synchronous openSync/readSync of the extension file — on every call. Compute the diagnosis once at mark-unavailable time (the single load-failure sink, run per Database not per request), cache it on ExtensionCapability, and have the warning read the cached result (falling back to the pure, no-I/O string classifier if it is absent). Loader capability-shape assertions relax from toEqual to toMatchObject for the new optional field. Addresses PR #2383 review finding F3. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * test(fts): cover the missing_dependency remedy on the --repair-fts path (#2374) The repair-fts error interpolates the classified remedy, but no test reached the missing_dependency branch — only the corrupt/invalid-ELF path. Add a Windows error-126 case asserting the thrown error carries the VC++ redistributable remedy and omits the old "retry the network install" tail, and that no index is dropped. Addresses PR #2383 review finding F6a (--repair-fts surface). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * refactor(fts): share the VC++ redistributable install hint (#2374) The Microsoft Visual C++ redistributable name and aka.ms URL were duplicated verbatim in WINDOWS_MISSING_DEPENDENCY_REMEDY and STRUCTURAL_MISSING_DEPENDENCY_REMEDY. Factor a single VC_REDIST_INSTALL_HINT constant so the pointer cannot drift between them; the composed remedy strings are byte-identical (existing exact-text assertions unchanged). Also adds a test covering the previously-unexercised structural remedy branch. Addresses PR #2383 review finding F5a. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * test(fts): guard FILE_CORRUPTION_SIGNATURES parity with the installer script (#2374) The corruption-signature list is deliberately duplicated between extension-load-error.ts and scripts/install-duckdb-extension.mjs (the .mjs cannot import the .ts), with nothing guarding against drift — a one-sided edit would desync the FORCE-INSTALL verb from remedy classification. Export the array from both and add a parity test that compares regex source + flags element-wise. Addresses PR #2383 review finding F5b. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * chore(test): run extension-binary-real in the sequential lbug-db vitest project (#2374) extension-binary-real.test.ts imports @ladybugdb/core but ran in the parallel `default` project, contrary to TESTING.md's rule that native-LadybugDB tests live in the sequential `lbug-db` project. Add it to the lbug-db include list and the default exclude list; it now runs under lbug-db and no longer under default. Addresses PR #2383 review finding F6c. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * test(fts): fail loud, not silent-skip, on missing FTS artifacts under REQUIRE_FTS=1 (#2374) The real-binary structural tests gated on raw .skipIf(!lbugNative) / .skipIf(!installedFts), so under GITNEXUS_REQUIRE_FTS=1 a missing artifact would silently vanish from a green CI run (the #2299 trap). These tests inspect the extension file directly and need its path, not a loaded connection — so skipUnlessFtsAvailable (which needs an initialized LadybugDB) does not fit. Add requireFtsResourceOrSkip: skip gracefully offline, throw under REQUIRE_FTS=1. The always-on process.execPath assertion still runs everywhere. Addresses PR #2383 review finding F6d. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * style(fts): apply prettier formatting to the #2383 fix files (#2374) Line-wrapping only; the quality/format CI check flagged three files. No behavior change. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
125 lines
5.1 KiB
JavaScript
125 lines
5.1 KiB
JavaScript
#!/usr/bin/env node
|
|
import fs from 'node:fs/promises';
|
|
import os from 'node:os';
|
|
import path from 'node:path';
|
|
import { createRequire } from 'node:module';
|
|
import { pathToFileURL } from 'node:url';
|
|
|
|
const EXTENSION_NAME_PATTERN = /^[A-Za-z][A-Za-z0-9_]*$/;
|
|
|
|
// Positive on-disk-corruption signatures. `FORCE INSTALL` re-downloads even when
|
|
// a file is already present; we only want that when the LOAD error proves the
|
|
// existing file is bad (truncated/wrong-platform, #2374). For everything else —
|
|
// a missing file (plain INSTALL downloads it), or a permanent non-file failure a
|
|
// re-download can never fix (missing runtime dep: "cannot open shared object") —
|
|
// plain INSTALL avoids re-downloading ~2 MB on every analyze run forever.
|
|
// Exported so a parity test keeps this byte-identical to the copy in
|
|
// src/core/lbug/extension-load-error.ts (this `.mjs` cannot import that `.ts`), #2383 F5b.
|
|
export const FILE_CORRUPTION_SIGNATURES = [
|
|
/invalid elf/i,
|
|
/file too short/i,
|
|
/not a valid/i,
|
|
/bad magic/i,
|
|
/wrong architecture/i,
|
|
/mach-o/i,
|
|
/truncat/i,
|
|
];
|
|
|
|
/**
|
|
* Decide the install verb from the LOAD error that triggered this install.
|
|
* `FORCE INSTALL` only when the error positively indicates file-level breakage;
|
|
* otherwise plain `INSTALL` (missing file, missing-dependency dlopen failure,
|
|
* or unknown/absent error).
|
|
*/
|
|
export function chooseInstallVerb(loadError) {
|
|
if (loadError && FILE_CORRUPTION_SIGNATURES.some((re) => re.test(loadError))) {
|
|
return 'FORCE INSTALL';
|
|
}
|
|
return 'INSTALL';
|
|
}
|
|
|
|
function parseLbugMaxDbSize(raw) {
|
|
const parsed = raw ? Number(raw) : NaN;
|
|
if (!Number.isFinite(parsed) || parsed <= 0) {
|
|
throw new Error(`Invalid LadybugDB max DB size for extension installer: ${raw ?? '<missing>'}`);
|
|
}
|
|
return Math.floor(parsed);
|
|
}
|
|
|
|
function resolveMaxDbSize() {
|
|
// argv[3] is the optional positional size; ignore it when it is actually a
|
|
// flag token (e.g. `--verify-only`) and fall back to the env default.
|
|
const sizeArg =
|
|
process.argv[3] && !process.argv[3].startsWith('--') ? process.argv[3] : undefined;
|
|
return parseLbugMaxDbSize(sizeArg ?? process.env.GITNEXUS_LBUG_MAX_DB_SIZE);
|
|
}
|
|
|
|
/** Open a scratch LadybugDB and return its connection plus a disposer. */
|
|
async function defaultConnect(lbugMaxDbSize) {
|
|
const require = createRequire(import.meta.url);
|
|
const lbugModule = require('@ladybugdb/core');
|
|
const lbug = lbugModule.default ?? lbugModule;
|
|
|
|
const tmpDir = await fs.mkdtemp(path.join(os.tmpdir(), 'gitnexus-ext-install-'));
|
|
const dbPath = path.join(tmpDir, 'install.lbug');
|
|
const db = new lbug.Database(dbPath, 0, false, false, lbugMaxDbSize);
|
|
const conn = new lbug.Connection(db);
|
|
return {
|
|
conn,
|
|
dispose: async () => {
|
|
await conn.close().catch(() => {});
|
|
await db.close().catch(() => {});
|
|
await fs.rm(tmpDir, { recursive: true, force: true }).catch(() => {});
|
|
},
|
|
};
|
|
}
|
|
|
|
/**
|
|
* Install (or verify) an optional LadybugDB extension in this short-lived process.
|
|
*
|
|
* @param {string} extensionName
|
|
* @param {object} [options]
|
|
* @param {boolean} [options.verifyOnly] LOAD-only Docker build gate — no install.
|
|
* @param {string} [options.loadError] The parent's LOAD failure; selects the verb.
|
|
* @param {(size: number) => Promise<{conn: {query: (sql: string) => Promise<unknown>}, dispose: () => Promise<void>}>} [options.connect]
|
|
* Connection factory; injectable for offline unit tests.
|
|
*/
|
|
export async function installDuckDbExtension(extensionName, options = {}) {
|
|
const { verifyOnly = false, loadError, connect } = options;
|
|
if (!extensionName || !EXTENSION_NAME_PATTERN.test(extensionName)) {
|
|
throw new Error(`Invalid DuckDB extension name: ${extensionName ?? '<missing>'}`);
|
|
}
|
|
|
|
const makeConnection = connect ?? (() => defaultConnect(resolveMaxDbSize()));
|
|
const { conn, dispose } = await makeConnection();
|
|
|
|
try {
|
|
if (verifyOnly) {
|
|
// Prove a previously-baked extension is resolvable by a FRESH process
|
|
// under the current HOME (the runtime `LOAD EXTENSION` path) — no INSTALL,
|
|
// no network. Used as a Docker build-time gate so a HOME/extension-dir
|
|
// mismatch fails the build instead of silently degrading search at runtime.
|
|
await conn.query(`LOAD EXTENSION ${extensionName}`);
|
|
console.log(
|
|
`[install-ext] LOAD-only verify OK for '${extensionName}' (HOME=${process.env.HOME})`,
|
|
);
|
|
} else {
|
|
// Plain INSTALL is a no-op when the file already exists; escalate to FORCE
|
|
// only when the LOAD error proves the on-disk file is broken (#2374).
|
|
await conn.query(`${chooseInstallVerb(loadError)} ${extensionName}`);
|
|
}
|
|
} finally {
|
|
await dispose();
|
|
}
|
|
}
|
|
|
|
// Only run when executed directly — imported (e.g. by unit tests) it stays inert.
|
|
if (import.meta.url === pathToFileURL(process.argv[1] ?? '').href) {
|
|
installDuckDbExtension(process.argv[2] ?? process.env.GITNEXUS_LBUG_EXTENSION_NAME, {
|
|
verifyOnly: process.argv.includes('--verify-only'),
|
|
loadError: process.env.GITNEXUS_LBUG_EXTENSION_LOAD_ERROR,
|
|
}).catch((err) => {
|
|
console.error(err instanceof Error ? (err.stack ?? err.message) : String(err));
|
|
process.exitCode = 1;
|
|
});
|
|
}
|