ci: bump ParadeDB image to v0.25.3 to fix flaky block read errors - #3554
Merged
Conversation
The pinned image (v0.21.12) predates paradedb/paradedb#4338, which fixes 'could not read blocks' errors when a BM25 query with a non-indexed predicate (our deleted_at filter) hits stale ctids after VACUUM truncation. Repeated fixture reloads in the feature tests trigger exactly that, making TestTaskSearchTitleBoost fail intermittently.
kolaente
enabled auto-merge (rebase)
August 19, 2026 06:43
Preview DeploymentPreview deployments for this PR are available at:
The preview environment will start automatically on first visit. Subsequent pushes to this PR will update the Run locally with Dockerdocker pull ghcr.io/go-vikunja/vikunja:pr-3554
docker run -p 3456:3456 ghcr.io/go-vikunja/vikunja:pr-3554Last updated for commit 0ad0a5c |
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.
test-api (paradedb, feature)fails intermittently inTestTaskSearchTitleBoostwithpq: could not read blocks 298..298 in file "base/16384/24802": read only 0 of 8192 bytes (XX001), cascading intocurrent transaction is abortedfor following subtests. Rerun usually passes.Cause: pg_search bug paradedb/paradedb#4333. BM25 query with non-indexed predicate (
deleted_at) takes heap_filter path, fetches all matching heap tuples. Repeated fixture reloads plus concurrent autovacuum truncate trailing heap pages, leaving stale ctids in the BM25 index pointing past end of relation. Pinned image was v0.21.12 (2026-03-05), one week before fix paradedb/paradedb#4338. Bump digest to currentlatest-pg17(v0.25.3).