mirror of
https://github.com/abhigyanpatwari/GitNexus.git
synced 2026-11-10 08:27:27 +00:00
347165dd59
* fix(lbug): bump @ladybugdb/core to 0.21.2 to stop doubled rows after delete and re-copy LadybugDB 0.21.0 and 0.21.1 return every row of a table that spans more than one native vector twice once the incremental writeback has DETACH DELETEd it and a COPY into an earlier table has run. NodeGroup::scan let a morsel that ended before the group's first live row wrap an unsigned subtraction and rescan to the end of the group (LadybugDB #1085, fixed in 0.21.2). No primary key error fires. The identity guard from #3442 stops the run with "unexpected or duplicate ID", so a Swift edit that pulls every importer into the write set failed on repos with more than 2048 structs. Only unreleased main was affected: 1.6.12 ships 0.18.3. Pin 0.21.2 in package.json, update the six @ladybugdb/core entries in the lockfile, and move coreVersion in the vendored FTS manifest. The FTS extension stays at 0.21.0 because no v0.21.1 or v0.21.2 artifact is published; the pairing assertion and its unit tests pass. Add a regression to the delete-nodes-for-files suite: 2049 structs with CONTAINS edges are loaded, every file is deleted, the graph is loaded again, and each id and edge must appear exactly once. Verification (Linux, Node 22.18): - lbug-delete-nodes-for-files: 11/11 on 0.21.2. With the 0.21.1 native packages swapped in, the new test fails with 4098 rows instead of 2049. - Reporter recipe end to end on the built CLI: incremental analyze exits 0 with no duplicate ids on a Swift-heavy fixture and on a 70-file Python fixture, with and without FTS. On 0.21.1 the Swift fixture exits 1. - A 0.21.1-written database opens and reads under 0.21.2. - prettier, eslint and typecheck:tests are clean on the changed files. - The full lbug-db project had not finished when this was committed. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> * fix(lbug): pair core and extensions at 0.22.0 Include the duplicate-row scan and relationship page-padding fixes. Use matching official FTS and VECTOR artifacts on all five platforms. Add a page-padding regression and document the storage 47 to 49 upgrade, including rollback and cached-embedding recovery limits. * fix(lbug): recognize pending checkpoint recovery * fix(bench): isolate indexes by runtime * fix(query): reject mixed symbol paths Printable paths could disagree with canonical symbol UIDs and pass NUL-only validation. Reject those tuples at response boundaries. Add Python/Swift MCP fault cases and a linked-worktree reproducer. Refs #3527 * fix(query): preserve provider semantic IDs * fix(lbug): clear analysis memory budget Restore the normal reader budget after indexing. The leaked adaptive hint exhausted the 0.22.0 pool during query and rename operations. Assert the budget is restored after real analyses, and give integrity cases unique CI audit identities. --------- Co-authored-by: Gergo Magyar <gergomagyar0@gmail.com> Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| bench | ||
| spikes | ||
| arm64-prebuild.cjs | ||
| assert-native-parsers.mjs | ||
| assert-publish-fts-coverage.cjs | ||
| assert-publish-grammar-coverage.cjs | ||
| assert-web-assets.mjs | ||
| bench-scope-resolution.ts | ||
| build-tree-sitter-grammars.cjs | ||
| build-web.js | ||
| build.js | ||
| cross-platform-tests.ts | ||
| ensure-fts.ts | ||
| execution-reporter.ts | ||
| install-duckdb-extension.mjs | ||
| owner-edge-guard-scaling.ts | ||
| prepare-tree-sitter-bundle.cjs | ||
| rebuild-bundled-grammar-prebuilds.cjs | ||
| repro-3527.mjs | ||
| run-benchmarks.ts | ||
| run-cross-platform.ts | ||
| shard-arg.ts | ||
| shard-timings-reporter.ts | ||
| shard-timings.ts | ||
| smoke-package-managers.mjs | ||
| sync-plugin-manifests.mjs | ||
| test-completeness.ts | ||