MultiHeadAttention::new() and RuvectorLayer::new() used assert!() for input
validation which caused fatal abort() when called from NAPI-RS/WASM bindings —
unrecoverable by JavaScript callers. Both now return Result<Self, GnnError>,
and all WASM/NAPI wrappers propagate errors as catchable JS exceptions.
Also fixes pre-existing mmap.rs test compilation error (grad_offset returns
Option<usize>, not usize).
Closes#216
Co-Authored-By: claude-flow <ruv@ruv.net>
Resolves merge conflicts in intelligence data files.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Run cargo fmt across all crates (468 files formatted)
- Add permissions for PR comments in benchmarks.yml
- Add continue-on-error for PR comment steps
- Remove Docker service from postgres-extension-ci (pgrx manages own postgres)
- Add permissions to postgres-extension-ci.yml
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* chore: Add proptest regression data from test run
Records edge cases found during property testing that cause
integer overflow failures. These will help reproduce and fix
the boundary condition bugs in distance calculations.
* fix: Resolve property test failures with overflow handling
- Fix ScalarQuantized::distance() i16 overflow: use i32 for diff*diff
(255*255=65025 overflows i16 max of 32767)
- Fix ScalarQuantized::quantize() division by zero when all values equal
(handle scale=0 case by defaulting to 1.0)
- Bound vector_strategy() to -1000..1000 range to prevent overflow in
distance calculations with extreme float values
All 177 tests now pass in ruvector-core.
* fix(cli): Resolve short option conflicts in clap argument definitions
- Change --dimensions from -d to -D to avoid conflict with global --debug
- Change --db from -d to -b across all subcommands (Insert, Search, Info,
Benchmark, Export, Import) to avoid conflict with global --debug
Fixes clap panic in debug builds: "Short option names must be unique"
Note: 4 CLI integration tests still fail due to pre-existing issue where
VectorDB doesn't persist its configuration to disk. When reopening a
database, dimensions are read from config defaults (384) instead of
from the stored database metadata. This is an architectural issue
requiring VectorDB changes to implement proper metadata persistence.
* feat(core): Add database configuration persistence and fix CLI test
- Add CONFIG_TABLE to storage.rs for persisting DbOptions
- Implement save_config() and load_config() methods in VectorStorage
- Modify VectorDB::new() to load stored config for existing databases
- Fix dimension mismatch by recreating storage with correct dimensions
- Fix test_error_handling CLI test to use /dev/null/db.db path
This ensures database settings (dimensions, distance metric, HNSW config,
quantization) are preserved across restarts. Previously opening an existing
database would use default settings instead of stored configuration.
* fix(ruvLLM): Guard against edge cases in HNSW and softmax
- memory.rs: Fix random_level() to handle r=0 (ln(0) = -inf)
- memory.rs: Fix ml calculation when hnsw_m=1 (ln(1) = 0 → div by zero)
- router.rs: Add division-by-zero guard in softmax for larger arrays
These edge cases could cause undefined behavior or NaN propagation.
---------
Co-authored-by: Claude <noreply@anthropic.com>
- Format all Rust code with cargo fmt
- Generate Cargo.lock for security audit
- Add build:wasm script to graph-wasm package.json
- Update npm/package-lock.json
The CI was failing due to:
1. Rust code formatting check failures
2. Missing Cargo.lock file for cargo audit
3. Missing build:wasm script expected by graph-ci.yml workflow
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
