Repository navigation
fix(deps): require sqlite-vec 0.1.7+ for 64-bit linux/arm64 wheels - #334
Open
hatemadi15 wants to merge 1 commit into
Open
hatemadi15 wants to merge 1 commit into
hatemadi15 wants to merge 1 commit into
Conversation
hatemadi15
marked this pull request as ready for review
November 9, 2026 19:42
This branch has not been deployed
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.
Fixes #65.
#67 switched the project's SQLite connection from
load_vec="auto"toload_vec=True. Under"auto", cocoindex swallows a failed extension load, so the failure only showed up later as the misleadingsqlite-vec extension must be loaded for vec0 virtual tables. Since #67 the real load error surfaces instead.The cause behind the report was still there. The linux aarch64 wheels of sqlite-vec 0.1.5 and 0.1.6 ship a 32-bit ARM
vec0.so, which a 64-bit Python cannot load:uv.lockstill pins 0.1.6 andpyproject.tomlallows>=0.1.0, souv syncon linux/arm64 still installs the broken binary, andpip install -U cocoindex-codekeeps a 0.1.6 that is already installed. 0.1.7 is the first stable release with a 64-bit aarch64 build; it came out on 2026-03-17, four days after this issue was filed. The reporter was inside a Docker Sandbox, which is linux/arm64 on an arm64 host such as Apple Silicon.This raises the floor to
sqlite-vec>=0.1.7and runsuv lock --upgrade-package sqlite-vec, which moves only sqlite-vec (0.1.6 to 0.1.9). Nothing else pins sqlite-vec. The Docker images, including the linux/arm64 ones the release job publishes, install withuv pip installfrom the source tree rather than from the lockfile. They have resolved a good wheel since 0.1.7 came out, and the floor keeps it that way.Validation
CI has no linux/arm64 runner (ubuntu x86_64, macOS arm64, Windows x86_64), so the arm64 evidence comes from inspecting and cross-installing the PyPI wheels. The inspected 0.1.6 aarch64 wheel and the five 0.1.9 wheels have the same sha256 as their entries in
main'suv.lockand in this branch's.vec0.soin themanylinux_2_17_aarch64wheel (file,readelf -h):vec0.soVersions before 0.1.5 publish no linux aarch64 wheel. The other 0.1.7 and 0.1.9 wheels are correct as well: manylinux x86_64 is ELF 64-bit x86-64, macOS is Mach-O 64-bit x86_64 and arm64, and win_amd64 is PE32+ x86-64. The 0.1.7 and 0.1.9 Linux builds need at most
GLIBC_2.17(aarch64) andGLIBC_2.14(x86_64), as their manylinux2014 tag promises.uv syncinstalls. I ranuv sync --frozen --no-dev --no-install-project --python-platform aarch64-unknown-linux-gnuinto a scratch env. Frommain's lock it installssqlite-vec==0.1.6, whosevec0.soisELF 32-bit LSB shared object, ARM, EABI5. Loading that into a 64-bit Python fails withwrong ELF class: ELFCLASS32; the ELF class check comes before the machine check, so an aarch64 host fails the same way. From this branch's lock it installssqlite-vec==0.1.9, whosevec0.soisELF 64-bit LSB shared object, ARM aarch64.uv sync --locked --no-devinto a fresh env installs sqlite-vec 0.1.9 without sentence-transformers or torch. I then ranccc init --litellm-model openai/text-embedding-3-small,ccc index,ccc statusandccc search(plain,--lang,--path,--json). After editing one file and deleting another, I re-indexed (1 deleted, 1 reprocessed, 1 unchanged), searched again and ranccc daemon stop. Embeddings came from LiteLLM against a local fake OpenAI endpoint, with a throwawayHOMEandCOCOINDEX_CODE_DIR. Every command exited 0, the deleted file dropped out of the results, anddaemon.loghad noERRORlines.pip install -Uof a package that requiressqlite-vec>=0.1.0keeps 0.1.6; requiring>=0.1.7upgrades it to 0.1.9 (pip 26.2.2).uv run pytest tests/(x86_64, Python 3.13) gives 350 passed, 8 deselected on 0.1.9 (this branch's lock), on 0.1.7 (installed by hand, the new floor) and onmainwith 0.1.6.tests/test_query_filters.pyruns the KNN, partition-key and full-scan query shapes against a real vec0 table, including the hidden-distancecontract, and passes on all three versions.uv run prek run --all-filespasses, including the pinneduv-lockhook and the pytest hook (350 passed).uv run ruff check .,uv run ruff format --check .anduv run mypy src/ tests/pass.uv run mypy .reports 2 errors inscripts/find_best_models.py, whichmainreports too.