mirror of
https://github.com/abhigyanpatwari/GitNexus.git
synced 2026-09-09 22:33:39 +00:00
* fix(schema): declare the full scope-resolution relation cross product (#2792) `RELATION_SCHEMA` was hand-listed, and every prior fix added only the FROM/TO pair named in a crash report — `Const→Method` in #2769, the Swift/Rust member pairs before it. So `analyze` kept aborting at `assertDeclaredPair` on the next codebase whose edges happened to land on a different pair; #2792 reports `Class→Variable` on Java. Audit the surface instead of the symptom. `buildGraphNodeLookup` skips any node whose label is not in `isLinkableLabel`, so the lookup holds only linkable-labelled nodes — and both endpoints of every graph-bridge edge resolve through that lookup. The emittable surface is therefore exactly: FROM LINKABLE_LABELS + File (the module-level caller fallback) TO LINKABLE_LABELS + CALL_TARGET_TYPES `isCallerAnchorLabel` is a strict subset of linkable and contributes nothing on top. `CALL_TARGET_TYPES` contributes `Delegate`, which `tryEmitEdgeWithExplicitTargetId` can emit without going through the lookup at all. Generate that 14x14 block into the DDL rather than listing it: 223 -> 322 declared pairs, and no future pair from these sets can be missing by construction. The containment/inheritance/DI/route/cluster/PDG pairs stay hand-declared — no single predicate describes them. Both label sets live in the ingestion layer, which `core/lbug` must not import, so schema.ts carries twin lists. test/unit/schema-pair-coverage.ts derives the requirement from the originals and fails CI when either set grows without the pairs landing here — the piecemeal loop this fix ends. Measured before widening: at 322 pairs the cost is inside noise (1.09s vs 1.12s per 300 anchored queries on a 32-table DB), but the full 32x32 cross product is ~1.8x on untyped-endpoint anchored queries. The audited subset is the right scope, not "declare everything". INCREMENTAL_SCHEMA_VERSION 34 -> 35: LadybugDB fixes endpoint pairs when the rel table is created, so a pre-v35 database physically cannot store these edges. Closes #2792 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * fix(schema): declare the non-bridge structural pairs COBOL and Vue emit The generated scope-resolution block closed the half of RELATION_SCHEMA a label predicate can describe. The hand-declared half was still stale: with #2791's Function->Variable fix applied, `analyze` continued to abort on this repo's own test/fixtures/lang-resolution with Relationship label pair Module→Property is not declared A full sweep (assertDeclaredPair patched to log-and-skip, run over the whole fixture corpus) found 13 undeclared pairs over 106 edges. This branch already covered 3 of them via the cross product; the remaining 10 come from emitters outside the graph bridge: - cobol-processor.ts mints Module / Namespace / Record / Property / CodeElement and wires them with CONTAINS, CALLS and ACCESSES (9 pairs) - vue-sfc-extractor.ts emits BINDS_EVENT_HANDLER from a handler Function to the child component's File, the only edge whose target is a File (1 pair) CodeElement, Namespace, Record and File are in neither scope-bridge label set, so neither the generated block nor schema-pair-coverage.test.ts can reach them. Adds test/integration/structural-pair-coverage.test.ts, which derives the requirement from a corpus instead of a predicate: it runs the real pipeline over the non-bridge fixtures and requires every FROM/TO pair they produce to be declared. Mutation-checked — dropping `FROM Function TO File` fails it with exactly Function|File. Verified: cobol-app, vue-basic and php-transitive-traits now index instead of aborting; the full lang-resolution corpus completes at 10,876 nodes / 18,517 edges; scrypster/muninndb at 0b7a4272 (the #2789 repro) completes at 20,069 nodes / 71,580 edges, matching #2791 exactly, so this supersedes that PR. * refactor(test): simplify the structural pair coverage guard Cleanup pass over the previous commit. No behaviour change to the schema. - reuse `FIXTURES` and `runPipelineFromRepo` from resolvers/helpers.ts instead of re-deriving the fixture root and importing pipeline.js directly - gate on `distWorkerExists()` like every other integration test that passes `workerUrlForTest`, so a missing dist skips rather than fails - run the three fixtures with `it.concurrent.each`; they share nothing and the cost is almost all worker spawn plus grammar load, which overlaps well (tests phase 21-24s -> 5.6s measured) - replace the sentinel-in-a-Set filter with a plain `.filter()` chain, matching the sibling unit test, and move the declared/table lookups off the per-edge path onto the deduped set - move the pure string pin out of the integration tier into schema-pair-coverage.test.ts, where the identical construct already lives, so it needs no build and survives fixture deletion - trim the schema and test prose that restated the code, and correct the BINDS_EVENT_HANDLER attribution: it is emitted by languages/vue/scope-resolver.ts, not vue-sfc-extractor.ts - amend the v35 comment to mention the 10 structural pairs it now also stamps Still mutation-checked: dropping `FROM Function TO File` now fails both the integration sweep and the unit pin with exactly Function|File. 89 tests green. * fix(schema): generate the attachment pair surface and close four analyze aborts Review of the generated scope-bridge cross product found four `analyze` hard-aborts still live at head, each reproduced end-to-end on the default user path (`analyze --index-only --skip-git`): Method→Annotation Spring `@Bean` + `@ConditionalOnMissingBean` (Java + Kotlin) Method→File Vue Options-API `methods:` handler bound to a child event Namespace→Record COBOL `DECLARATIVES` / `USE AFTER STANDARD ERROR ON <file>` Class→Tool `@mcp.tool()` applied to a class All four are pre-existing on main, and both existing guards were structurally blind to them: the unit guard derives from LINKABLE_LABELS ∪ CALL_TARGET_TYPES (none of Annotation/Tool/Record/File-as-target is a member) and the corpus guard ran three fixtures that exercise none of these emitters. All 16 tests passed while all four crashes were live. The PR's model — "bridge endpoint × structural endpoint" — does not fit: Namespace→Record is structural on both sides. The property that does hold is that the ANCHOR is a lookup result, not a literal at the emit site, so the emitter cannot constrain its label. That gives a second closed-form rule: DEFINITION_ANCHOR_LABELS × ATTACHMENT_TARGET_LABELS DEFINITION_ANCHOR_LABELS is derived from NODE_TABLES by subtraction, so a new node table joins automatically. 332 → 450 declared pairs. Sized against a committed harness (gitnexus/bench/schema-pairs), real @ladybugdb/core, identical data: 450 costs 0.93–1.05× of 332 on untyped-endpoint anchored queries — inside noise — versus 1.22–1.43× at 641 and 2.03–2.34× at 1024. The harness reproduces the known #2792 cliff, which is what makes the 450 figure trustworthy. Also in this change: - Delete the 161 hand-declared pairs the rules already generate (233 → 72). The declared set is byte-identical at 450; those lines were load-bearing shadow, because the generator suppresses anything already declared structurally, so narrowing a rule later would silently keep pairs alive. A new guard fails CI if a hand-declared pair is ever re-added inside a rule. - Import LINKABLE_LABELS / CALL_TARGET_TYPES instead of hand-copying them. The twins' stated justification ("the ingestion layer must not be imported here") is false: csv-generator.ts and lbug-adapter.ts, siblings in the same directory, already do, and no rule in AGENTS.md / ARCHITECTURE.md / CONTRIBUTING.md / GUARDRAILS.md states otherwise. - Resolve `resolveStreamGraphEmit` after the guards that rebind `options.force`, not at function entry. It gates on `force`, and every freshness guard runs ~360 lines later, so the v34→v35 bump would have pushed every existing index down the non-streamed emit path — losing the #2680 memory streaming added for the #2649 kernel-scale OOM, for exactly the population most likely to be memory-constrained. - `UndeclaredRelationPairError` now carries the relationship type, both node ids and the source file, with a matching CLI branch. The old message named only the abstract label pair, which a user could not act on. Found through the cause chain, since pipeline-phases/runner.ts rewraps every phase failure. - Share one classifier (`relPairKeyFor`) across the router, both emit sinks and the corpus guard, which previously hand-mirrored the router's skip rule; one cause-chain walker in lib/utils.ts; one exported pair-matching regex. - Corpus guard: four new fixtures reproducing the aborts, per-fixture sentinel pairs so a fixture that stops emitting fails loudly instead of passing vacuously on an empty graph. The per-edge path stays allocation-free: the failure context is passed positionally and the message is built only inside the throw. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0182jkjQqzACkJKYw4MLDnhX * test(bench): re-baseline the COBOL capture fingerprint for the new fixture `bench/scope-capture` globs `lang-resolution/cobol-*`, so the `cobol-declaratives` fixture added in81daf370e(to reproduce the `Namespace→Record` analyze abort) joined that corpus and shifted the fingerprint — 14 → 15 files. Verified corpus-only, not a capture change: with that one fixture moved aside the fingerprint is byte-identical to the prior baseline (d45bb091…), and81daf370etouches no COBOL capture code. The new value reproduces CI's reported hash exactly. Scaling 0.677 < 1.5 budget. `bench/scope-capture/measure.mjs --check` → PASS (15 languages). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0182jkjQqzACkJKYw4MLDnhX --------- Co-authored-by: Gergo Magyar <gergomagyar0@gmail.com> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
169 lines
7.5 KiB
TypeScript
169 lines
7.5 KiB
TypeScript
/**
|
|
* Tests for the undeclared FROM→TO label-pair failure path in the
|
|
* `analyzeCommand` CLI (#2789).
|
|
*
|
|
* `assertDeclaredPair` aborts the run when an extracted edge's endpoint-label
|
|
* pair is missing from GitNexus's own relation DDL — deliberately, because the
|
|
* alternative is a late `COPY` failure that silently drops edges. Before this
|
|
* branch existed the user got `Analysis failed` plus a stack trace through
|
|
* GitNexus internals: no file, no relationship, and an implicit "try again"
|
|
* that can never work. The CLI must instead name the pair, the relationship
|
|
* type and the offending file, and point at an issue report.
|
|
*
|
|
* The CLI does NOT compose that text: it prints `err.message` indented (the
|
|
* `LbugWipeError` idiom in the same catch block), because the message is
|
|
* self-contained — `gitnexus serve` forwards only `err.message` over worker
|
|
* IPC, so anything rendered here instead would be invisible to serve users.
|
|
* The needles below are therefore the SAME strings
|
|
* `test/unit/rel-pair-routing.test.ts` pins on the message itself.
|
|
*
|
|
* Mirrors analyze-http-endpoint-error.test.ts:
|
|
* - vi.mock the heavy dependencies so no real DB / git is touched
|
|
* - drive `analyzeCommand` with a mocked `runFullAnalysis` that rejects
|
|
* - assert on process.exitCode and the captured logger records
|
|
*/
|
|
import { beforeEach, describe, expect, it, vi } from 'vitest';
|
|
|
|
const runFullAnalysisMock = vi.fn();
|
|
|
|
vi.mock('../../src/core/run-analyze.js', () => ({
|
|
runFullAnalysis: runFullAnalysisMock,
|
|
}));
|
|
|
|
vi.mock('../../src/core/lbug/lbug-adapter.js', () => ({
|
|
closeLbug: vi.fn(async () => undefined),
|
|
closeLbugBeforeExit: vi.fn(async () => undefined),
|
|
isLbugReady: vi.fn(() => false),
|
|
LbugWipeError: class LbugWipeError extends Error {},
|
|
}));
|
|
|
|
vi.mock('../../src/storage/repo-manager.js', () => ({
|
|
getStoragePaths: vi.fn(() => ({ storagePath: '.gitnexus', lbugPath: '.gitnexus/lbug' })),
|
|
getGlobalRegistryPath: vi.fn(() => 'registry.json'),
|
|
RegistryNameCollisionError: class RegistryNameCollisionError extends Error {},
|
|
AnalysisNotFinalizedError: class AnalysisNotFinalizedError extends Error {},
|
|
assertAnalysisFinalized: vi.fn(async () => undefined),
|
|
}));
|
|
|
|
vi.mock('../../src/storage/git.js', () => ({
|
|
getGitRoot: vi.fn(() => '/repo'),
|
|
hasGitDir: vi.fn(() => true),
|
|
}));
|
|
|
|
vi.mock('../../src/core/ingestion/utils/max-file-size.js', () => ({
|
|
getMaxFileSizeBannerMessage: vi.fn(() => null),
|
|
}));
|
|
|
|
// analyze.ts imports isHfDownloadFailure from hf-env.js — mock it to break the
|
|
// transitive gitnexus-shared chain (same reason as the sibling suite).
|
|
vi.mock('../../src/core/embeddings/hf-env.js', () => ({
|
|
isHfDownloadFailure: vi.fn(() => false),
|
|
}));
|
|
|
|
const PAIR_ERROR_ARGS = [
|
|
'Method|Annotation',
|
|
'ANNOTATED_BY',
|
|
'Method:src/main/java/app/BeanConfig.java:BeanConfig.dataSource#42',
|
|
'Annotation:src/main/java/app/BeanConfig.java:ConditionalOnMissingBean',
|
|
] as const;
|
|
|
|
describe('analyzeCommand undeclared relation-pair handling (#2789)', () => {
|
|
beforeEach(() => {
|
|
vi.resetModules();
|
|
runFullAnalysisMock.mockReset();
|
|
process.exitCode = undefined;
|
|
process.env.NODE_OPTIONS = `${process.env.NODE_OPTIONS ?? ''} --max-old-space-size=8192`.trim();
|
|
});
|
|
|
|
it('renders an actionable schema-gap message naming the pair, relationship, ids and file', async () => {
|
|
const { UndeclaredRelationPairError } = await import('../../src/core/lbug/rel-pair-routing.js');
|
|
runFullAnalysisMock.mockRejectedValue(new UndeclaredRelationPairError(...PAIR_ERROR_ARGS));
|
|
|
|
const { _captureLogger } = await import('../../src/core/logger.js');
|
|
const cap = _captureLogger();
|
|
const { analyzeCommand } = await import('../../src/cli/analyze.js');
|
|
|
|
await analyzeCommand(undefined, {});
|
|
|
|
expect(process.exitCode).toBe(1);
|
|
const record = cap.records().find((r) => r.recoveryHint === 'undeclared-relation-pair');
|
|
cap.restore();
|
|
|
|
expect(record).toMatchObject({
|
|
recoveryHint: 'undeclared-relation-pair',
|
|
labelPair: 'Method|Annotation',
|
|
relationType: 'ANNOTATED_BY',
|
|
sourceFile: 'src/main/java/app/BeanConfig.java',
|
|
});
|
|
// The CLI renders `err.message` indented (the `LbugWipeError` idiom) rather
|
|
// than re-formatting the structured fields, so these needles are the ONE
|
|
// wording — `test/unit/rel-pair-routing.test.ts` pins the same strings on
|
|
// the message itself and a reword updates one place, not two.
|
|
// Filter-to-empty, not an array of booleans: the failure output NAMES the
|
|
// missing string instead of making you count positions.
|
|
const text = typeof record?.msg === 'string' ? record.msg : '';
|
|
const required = [
|
|
'Method → Annotation',
|
|
'ANNOTATED_BY',
|
|
'src/main/java/app/BeanConfig.java',
|
|
'Method:src/main/java/app/BeanConfig.java:BeanConfig.dataSource#42',
|
|
'Annotation:src/main/java/app/BeanConfig.java:ConditionalOnMissingBean',
|
|
// Names it as a GitNexus gap, tells the user a re-run is pointless, and
|
|
// points at both actionable next steps.
|
|
"gap in GitNexus's own relation schema",
|
|
're-running the analysis will fail',
|
|
'https://github.com/abhigyanpatwari/GitNexus/issues/new',
|
|
'.gitnexusignore',
|
|
];
|
|
expect(required.filter((needle) => !text.includes(needle))).toEqual([]);
|
|
});
|
|
|
|
it('still fires when the ingestion phase runner has rewrapped it as a cause', async () => {
|
|
// The guard throws inside an emit phase, and the phase runner rewraps every
|
|
// phase failure as `new Error("Phase 'X' failed: …", { cause })` — a bare
|
|
// instanceof check at the CLI boundary would miss it entirely.
|
|
const { UndeclaredRelationPairError } = await import('../../src/core/lbug/rel-pair-routing.js');
|
|
const original = new UndeclaredRelationPairError(...PAIR_ERROR_ARGS);
|
|
// The wrapper deliberately does NOT interpolate the cause's message: the
|
|
// branch must render `undeclaredPair.message`, i.e. the message of the link
|
|
// it FOUND in the chain, not the outer wrapper's message.
|
|
runFullAnalysisMock.mockRejectedValue(
|
|
new Error(`Phase 'graph-emit' failed`, { cause: original }),
|
|
);
|
|
|
|
const { _captureLogger } = await import('../../src/core/logger.js');
|
|
const cap = _captureLogger();
|
|
const { analyzeCommand } = await import('../../src/cli/analyze.js');
|
|
|
|
await analyzeCommand(undefined, {});
|
|
|
|
expect(process.exitCode).toBe(1);
|
|
const records = cap.records();
|
|
cap.restore();
|
|
|
|
const record = records.find((r) => r.recoveryHint === 'undeclared-relation-pair');
|
|
expect(record).toMatchObject({ labelPair: 'Method|Annotation' });
|
|
const text = typeof record?.msg === 'string' ? record.msg : '';
|
|
expect(
|
|
['Method → Annotation', '.gitnexusignore'].filter((needle) => !text.includes(needle)),
|
|
).toEqual([]);
|
|
// The generic large-repo / module-not-found guidance must not also appear.
|
|
expect(records.some((r) => r.recoveryHint === 'large-repo')).toBe(false);
|
|
expect(records.some((r) => r.recoveryHint === 'module-not-found')).toBe(false);
|
|
});
|
|
|
|
it('does not claim an unrelated failure', async () => {
|
|
runFullAnalysisMock.mockRejectedValue(new Error('LadybugDB write failed'));
|
|
|
|
const { _captureLogger } = await import('../../src/core/logger.js');
|
|
const cap = _captureLogger();
|
|
const { analyzeCommand } = await import('../../src/cli/analyze.js');
|
|
|
|
await analyzeCommand(undefined, {});
|
|
|
|
expect(process.exitCode).toBe(1);
|
|
const records = cap.records();
|
|
cap.restore();
|
|
expect(records.some((r) => r.recoveryHint === 'undeclared-relation-pair')).toBe(false);
|
|
});
|
|
});
|