Repository navigation
feat: add shared e-means clustering and ecosystem integrations - #1489
Merged
Merged
Conversation
…add release metadata - ruvector-core ProductQuantized::encode keeps the existing f32 ordering for finite distances; f64 is used only when an f32 squared distance overflows. Adds a regression test with a pair that ties in f32 but not in f64. - Pin new 0.x edges exactly: rand_chacha =0.3.1, rand_core =0.6.4 and ruvector-e-means =0.1.0 in core, pq-search and rairs. - @ruvector/core: e-means moves from optionalDependencies to dependencies, since clustering.mjs re-exports it statically and has no fallback. - e-means MetaHarness accepts Darwin 0.13.0 and 0.13.1 (both run). ruvector resolves ^0.13.0 to 0.13.1, which made tuneClustering throw through ruvector/clustering. The receipt reports the version actually loaded. - cloudflare/build imports esbuild lazily and explains a missing install. - ADR-356 metadata for ruvector-e-means and @ruvector/e-means (homepage, bugs, keywords, description, animated SVG). READMEs no longer state unreleased ruv-FANN or consumer facades as available; crate README links are absolute. - ADR-359 labels the author's speedups as measured against an earlier build that is not in the tree, and adds an independent reproduction of the pruning change with matching output digests. Co-Authored-By: claude-flow <ruv@ruv.net>
Owner
Author
|
Main-red evidence before merge (head 9864a65): 62 pass, 4 skipped, 1 fail. The only red job is 🤖 Generated with claude-flow |
ruvnet
added a commit
that referenced
this pull request
Nov 11, 2026
… ruvector-core 2.5.2, ruvector-pq-search 2.3.1, ruvector-rairs 0.1.1 (#1491) Ships the e-means clustering subpaths and training APIs from #1489, now that ruvector-e-means 0.1.0 and @ruvector/e-means 0.1.0 are published. @ruvector/all: #1489 added @ruvector/e-means as a dependency and new files without updating the umbrella's manifest test, so two tests failed. e-means is now an ESM member (all.loadEMeans()), and the test accepts exact pins for new 0.x edges alongside caret ranges. ruvector: test/rabitq-optional.js guards the hard-dependency list; it now lists @ruvector/e-means, the deliberate edge #1489 added for ruvector/clustering.mjs. Unreleased changes also shipped by the crate bumps: - ruvector-core: generated-ID reservation, live HNSW identity retention, memory batch validation (each with tests), fuzz lockfile refresh. - ruvector-pq-search: Rust 1.88 MSRV fallback in codebook.rs. - ruvector-rairs: clippy allowance, crates.io keyword length fix.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a shared implementation of e-means (arXiv:2611.09501v1) for centroid/codebook training, with one Rust numerical kernel compiled to portable WASM. Existing Lloyd and neural-training defaults remain available.
Changes
ruvector-e-means0.1.0 with scaling-law defaults, EMA updates, cosine scheduling, weighted donor revival, both main finalizers, checked PQ/IVF modules, and exact distance pruning.@ruvector/e-means0.1.0 with typed-array result transfer, explicit runtime/quantization/IVF/MetaHarness/Cloudflare subpaths, and installed-archive qualification.Validation
@ruvector/core,ruvector,@ruvector/all, and the current@ruvector/wasmsource.Qualification is targeted: unrelated consumer root/prepack release builds and the whole monorepo matrix are not certified. The existing Darwin-only npm workspace blocks a whole-workspace Linux install; the integration tooling has its own reviewed lockfile. Browser Chromium qualification remains pending after independent startup failures.
Release order
The shared crate and npm package are not published by this PR. Publish and verify both 0.1.0 dependencies before releasing dependent consumer versions. Hosted Cloudflare deployment and live Vectorize writes remain pending.
Companion consumer change: ruvnet/ruv-FANN#227 (draft until the shared registry dependencies are published).
Review (lane 2026-11-11aq)
Fixed on the branch (commit 9864a65):
ruvector-coreProductQuantized::encodehad moved from f32 to f64 ordering, which changes codes for existing users at f32 near-ties (1 in 80,000 random 256-entry lookups flipped). It now keeps the f32 ordering for finite distances and uses f64 only when an f32 distance overflows. A regression test pins a tie case.rand_chacha =0.3.1,rand_core =0.6.4,ruvector-e-means =0.1.0).@ruvector/corelists e-means as a dependency rather than optional, sinceclustering.mjsre-exports it statically.tuneClusteringthrew throughruvector/clusteringbecauseruvectorresolves Darwin^0.13.0to 0.13.1 and e-means required exactly 0.13.0. Both versions run; the peer and guard now accept exactly 0.13.0 or 0.13.1.cloudflare/buildloads esbuild lazily, with a clear error when it is missing.Verified: the shipped
.wasmrebuilds byte-for-byte from source (Rust 1.99.1, wasm-bindgen 0.2.125). Rust tests, strict clippy,cargo package, 44 npm tests, typecheck, packed-consumer and ecosystem-consumer tests pass. No secrets in fixtures or receipts.CI note:
Build,npm-publish-pipeline (npm/packages/ruvector)andoptional-deps-resolvable-on-npmfail with E404 because consumers depend on the unpublished@ruvector/e-means@0.1.0. These failures come from this PR (they are green on main), so they block merge until the leaf package is on npm.cargo denyfails identically on main (#1487).🤖 Generated with claude-flow