Repository navigation
Conversation
The Docker Hub image was stuck at 2.0.5 because every publish run failed at login: the workflow read DOCKERHUB_USERNAME/DOCKERHUB_TOKEN (never set) and targeted the nonexistent `ruvector/` namespace instead of `ruvnet/`. - push to ruvnet/ruvector-postgres, auth with DOCKER_PERSONAL_ACCESS_TOKEN - only run on ruvector-postgres-v* releases or manual dispatch, so esp32/rvf/ crates releases can no longer retag :latest - strip the ruvector-postgres-v prefix when deriving the version from a tag - RUST_VERSION 1.83 -> 1.85 (the build-arg overrode the Dockerfile's 1.85, which edition2024 deps need) - Dockerfile labels/workspace version 0.3.1/2.0.4 -> 2.0.6 Co-Authored-By: claude-flow <ruv@ruv.net>
The image built without a lockfile, so cargo resolved the newest crates (icu_* 2.3 needs rustc 1.88) and the build failed on the 1.86 toolchain. Copy the crate's Cargo.lock into the build workspace, install the cargo-pgrx version that matches the pinned pgrx (0.12.9, as CI does), and keep the workflow's RUST_VERSION in step with the Dockerfile (1.86). Verified locally: pg17 image builds, CREATE EXTENSION works, ruvector_version() = 2.0.6, HNSW index scan and IVFFlat build succeed. Co-Authored-By: claude-flow <ruv@ruv.net>
Contributor
Benchmark Results SummaryDistance Function BenchmarksHNSW Index BenchmarksQuantization BenchmarksSee full results in the artifacts. |
Contributor
Benchmark ComparisonDistance BenchmarksBaseline (main)Current (PR) |
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
1 participant
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.
Docker Hub
ruvnet/ruvector-postgreshas been stuck at 2.0.5 (March) — everyDocker Hub Publishrun since has failed at login.Causes fixed
DOCKERHUB_USERNAME/DOCKERHUB_TOKEN(never set) and pushed to the nonexistentruvector/namespace → nowruvnet/, auth viaDOCKER_PERSONAL_ACCESS_TOKEN.ruvector-postgres-v*tags or manual dispatch, so other releases can't retag:latest.icu_*2.3 (rustc 1.88) and failed on 1.86. Now copies the crate'sCargo.lock;cargo-pgrx0.12.6 → 0.12.9 to match pinned pgrx.RUST_VERSION1.83 overrode the Dockerfile's 1.86 → aligned to 1.86.Verified locally (pg17, amd64): image builds,
CREATE EXTENSION ruvector,ruvector_version()= 2.0.6, HNSW index scan returns correct neighbours, IVFFlat index builds.Before publishing: the Docker Hub PAT in GCP Secret Manager is expired and the repo has no
DOCKER_PERSONAL_ACCESS_TOKENsecret — a new token must be added first.Not in scope: the extension's SQL default_version is still
0.3.0(pre-existing version tangle).🤖 Generated with claude-flow