GitNexus/gitnexus/vendor/lbug-vector
Gergő Magyar 347165dd59
fix(lbug): upgrade core and bundled extensions to 0.22.0 (#3578)
* 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>
2026-10-31 15:29:45 +00:00
..
prebuilds fix(lbug): upgrade core and bundled extensions to 0.22.0 (#3578) 2026-10-31 15:29:45 +00:00
LICENSE chore(deps): consolidate updates and vendor compatible VECTOR (#3709) 2026-10-24 14:42:43 +01:00
manifest.json fix(lbug): upgrade core and bundled extensions to 0.22.0 (#3578) 2026-10-31 15:29:45 +00:00
README.md fix(lbug): upgrade core and bundled extensions to 0.22.0 (#3578) 2026-10-31 15:29:45 +00:00

LadybugDB VECTOR artifacts

These unmodified binaries come from the official LadybugDB v0.22.0 build, at core commit 4ca22377b85a33a10247410fe3944a5224b1169d and extensions commit 119912e604ebbaad64072a701698d6fcf4140051.

manifest.json records each GitHub artifact ID, the archive digest supplied by GitHub, and the extracted binary's SHA-256. Every archive was checked against that digest before extracting vector/libvector.lbug_extension.

The CDN compatibility path can serve a VECTOR binary built against incompatible core symbols. Load the matching packaged artifact first so vector indexes work without a network install or a mutable home-cache copy. The existing never policy still disables the extension; missing artifacts retain the normal named-load and install fallback.

To refresh, select an official build matching the exact @ladybugdb/core pin, download its platform artifacts, verify their GitHub archive digests, and update the binaries and manifest together. Validate Linux, macOS, and Windows native tests before changing the pin. Do not substitute a nightly binary.

For example, the Linux x64 archive is available with:

gh api repos/LadybugDB/ladybug/actions/artifacts/12584987551/zip > vector-linux.zip

GitHub Actions artifacts expire; the committed binaries and checksums preserve the verified build. test/unit/vector-artifact-coverage.test.ts checks the core pin, platform coverage, and binary digests. The upstream MIT license is included in LICENSE.