Repository navigation
CI: pin the scale-test pgvector image to 0.8.7 (#977) - #987
Merged
Merged
Conversation
The fleet's host Postgres moved from pgvector 0.8.2 to 0.8.7 under mkreyman/infra#280; the scale-test job's service image moves in step, pinned by digest to the 0.8.7-pg16-trixie image already pulled on beelink (2026-10-13), so the job still never pulls from Docker Hub. Above the 0.8.4 floor (#965), so the insert/VACUUM race is gone and test_helper's below-floor warning no longer fires on beelink/nuc runs.
Owner
Author
|
Review round 1 (code) counted at |
A new advisory published since #981 — CVE-2026-105660 (MEDIUM, HTTP/1 request-target authority, GHSA-v53v-9hvg-37jf) — failed `mix hex.audit` in the commit hook for every branch. Bandit 1.13.0 fixed it, and OSV reports 1.13.1 clean of every advisory 1.12.5 carried, including CVE-2026-105659 (HTTP/2), so the #981 ignore entry comes out too. The endpoint still serves no HTTP/2 (`http_2_options: [enabled: false]`; Fly's proxy speaks HTTP/1.1 anyway) and endpoint_http2_test.exs keeps that under test, with @acknowledged_bandit moved to 1.13.1. thousand_island 1.5.0 -> 1.6.0 and hpax 1.0.4 -> 1.1.0 ride along as bandit's raised requirements.
…nding)
vacuum_vector_indexes/1's doc still described the infra#280 host-image move as
pending ("until the hosts move"), but the hosts now run 0.8.7 and CI's
scale-test job pins 0.8.7. A below-floor failure now reads as "upgrade the
image", not "wait for infra".
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.
Closes #977. Claim
handoff:loopctl:scale-test-pgvector-087context: mkreyman/infra#280 moved the fleet's host Postgres to pgvector 0.8.7; this moves the scale-test job's service pin in step.services.postgres.image→pgvector/pgvector@sha256:40d828eda66737aaacb934387a337babf1455ebd56e9bdd13fc08e211257c972(tag0.8.7-pg16-trixie), already pulled on beelink (2026-10-13), so the job still never pulls from Docker Hub.test_helper's below-floor warning stops firing there).Check after merge (from the issue): the scale-test job's
Initialize containerslog shows the new digest, and the below-0.8.4 warning no longer prints on beelink/nuc runs.