Q: Why does zvec close() modify index files even when the collection is opened with read_only=True?

This is a known bug in zvec 0.7.0 (Python) and 0.7.2 (Rust bindings). Closing a read-only Flat or HNSW index unconditionally flushed internal metadata, rewriting the `update_time` fields and `footer_crc` checksum in `.proxima` files (typically ~6 bytes per file). No data loss or incorrect query results occur, but content-hash/immutability checks fail. **Fix:** Upgrade zvec — the fix was merged into `main` via PR #834. Read-only close now skips metadata writes (timestamp/checksum updates) unless the index is dirty, with regression tests verifying byte-for-byte file immutability across open/close cycles. **Workaround for affected versions (0.7.0/0.7.2):** Do not rely on byte-level file hashes of `.proxima` index files for integrity checks; hash only the vector payload or track document IDs instead. Note the write only triggers on the final close that releases the native handle — repeated queries on a cached read-only handle do not modify files.

Q: How to fix CMake error "Target zvec_ailego is required by zvec_ailego_shared" when building zvec on Windows ARM64 with MSVC?

This configure-time failure affects zvec 0.5.1 on Windows ARM64 with the MSVC toolset. `src/ailego/CMakeLists.txt` calls `return()` early on the MSVC ARM64 path, so the static target `zvec_ailego` is never created, while `BUILD_ZVEC_AILEGO_SHARED=ON` (default) still references it and CMake fatals. Fix: upgrade zvec to a build from main that includes PR #352 (merged), which fixes the ailego CMake and architecture-macro handling for MSVC ARM64. Workarounds on 0.5.1: (1) configure with `-DBUILD_ZVEC_AILEGO_SHARED=OFF` so the missing static target is not referenced; (2) build the ARM64 native with GCC/Clang (Linux) or AppleClang (macOS Apple Silicon) instead, which are unaffected; or (3) patch `src/ailego/CMakeLists.txt` locally to remove the MSVC `return()` and use MSVC-compatible ARM64 flags instead of GCC-style `-march=armv8-a`.

Q: How to fix SIGSEGV native stack overflow crash in zvec QueryNode when using excludedFileTypes with large collections?

This crash is fixed upstream in PR #694 (merged). Upgrade `@zvec/zvec` and the matching native bindings (e.g. `@zvec/bindings-linux-x64`) to the release that includes the fix, then retry your query. Until you can upgrade, work around it by removing `excludedFileTypes` from `session.context()` calls: zvec-grep's `searchPlanToStorageFilter` expands the exclusion into one `file_id = '...' OR ...` predicate per file (~15k predicates for a 16k-file workspace), and the recursive sqlengine QueryNode parser overflows the Linux x64 stack. Queries without the file-type exclusion return normally on the same index.

Question 1

How to fix MSVC C1001 internal compiler error on Windows ARM64 with MSVC 19.51 (VS 2026) when compiling with /O2?

Accepted Answer

This is an MSVC 19.51 (VS 18.6) ARM64 optimizer regression, not a code bug — code that compiled with MSVC 19.44 crashes cl.exe with `fatal error C1001` when a loop accumulating `static_cast(codes[i]) * codes[i]` into an `int64_t` is inlined into callers with constant-filled vectors under `/O2 /Ob2`. Workarounds (any one works): 1. Widen the multiplication operand to 64-bit (result is identical): ```cpp sum_squared += static_cast(codes[i]) * codes[i]; // instead of static_cast(codes[i]) * codes[i] ``` 2. Disable vectorization for the loop: ```cpp #pragma loop(no_vector) for (size_t i = 0; i < codes.size(); ++i) { ... } ``` 3. Split the accumulation into a separate loop. Alternatively, pin/downgrade the toolchain to MSVC 14.44 (cl 19.44) until Microsoft fixes the regression. Reproducible on Compiler Explorer with `arm64 msvc v19.51 VS18.6`, flags `/DNDEBUG /O2 /Ob2 /EHsc -std:c++17 -MT /Zc:preprocessor /Zc:__cplusplus /W3`.

Question 2

Why does zvec close() modify index files even when the collection is opened with read_only=True?

Accepted Answer

This is a known bug in zvec 0.7.0 (Python) and 0.7.2 (Rust bindings). Closing a read-only Flat or HNSW index unconditionally flushed internal metadata, rewriting the `update_time` fields and `footer_crc` checksum in `.proxima` files (typically ~6 bytes per file). No data loss or incorrect query results occur, but content-hash/immutability checks fail.

**Fix:** Upgrade zvec — the fix was merged into `main` via PR #834. Read-only close now skips metadata writes (timestamp/checksum updates) unless the index is dirty, with regression tests verifying byte-for-byte file immutability across open/close cycles.

**Workaround for affected versions (0.7.0/0.7.2):** Do not rely on byte-level file hashes of `.proxima` index files for integrity checks; hash only the vector payload or track document IDs instead. Note the write only triggers on the final close that releases the native handle — repeated queries on a cached read-only handle do not modify files.

Question 3

How to fix CMake error "Target zvec_ailego is required by zvec_ailego_shared" when building zvec on Windows ARM64 with MSVC?

Accepted Answer

This configure-time failure affects zvec 0.5.1 on Windows ARM64 with the MSVC toolset. `src/ailego/CMakeLists.txt` calls `return()` early on the MSVC ARM64 path, so the static target `zvec_ailego` is never created, while `BUILD_ZVEC_AILEGO_SHARED=ON` (default) still references it and CMake fatals. Fix: upgrade zvec to a build from main that includes PR #352 (merged), which fixes the ailego CMake and architecture-macro handling for MSVC ARM64. Workarounds on 0.5.1: (1) configure with `-DBUILD_ZVEC_AILEGO_SHARED=OFF` so the missing static target is not referenced; (2) build the ARM64 native with GCC/Clang (Linux) or AppleClang (macOS Apple Silicon) instead, which are unaffected; or (3) patch `src/ailego/CMakeLists.txt` locally to remove the MSVC `return()` and use MSVC-compatible ARM64 flags instead of GCC-style `-march=armv8-a`.

Question 4

How to fix SIGSEGV native stack overflow crash in zvec QueryNode when using excludedFileTypes with large collections?

Accepted Answer

This crash is fixed upstream in PR #694 (merged). Upgrade `@zvec/zvec` and the matching native bindings (e.g. `@zvec/bindings-linux-x64`) to the release that includes the fix, then retry your query. Until you can upgrade, work around it by removing `excludedFileTypes` from `session.context()` calls: zvec-grep's `searchPlanToStorageFilter` expands the exclusion into one `file_id = '...' OR ...` predicate per file (~15k predicates for a 16k-file workspace), and the recursive sqlengine QueryNode parser overflows the Linux x64 stack. Queries without the file-type exclusion return normally on the same index.

zvec

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects