Skip to content

ci: bump ParadeDB image to v0.25.3 to fix flaky block read errors - #3554

Merged
kolaente merged 1 commit into
mainfrom
paradedb-test-flakiness
Aug 19, 2026
Merged

ci: bump ParadeDB image to v0.25.3 to fix flaky block read errors#3554
kolaente merged 1 commit into
mainfrom
paradedb-test-flakiness

Conversation

@tink-bot

Copy link
Copy Markdown
Collaborator

test-api (paradedb, feature) fails intermittently in TestTaskSearchTitleBoost with pq: could not read blocks 298..298 in file "base/16384/24802": read only 0 of 8192 bytes (XX001), cascading into current transaction is aborted for 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 current latest-pg17 (v0.25.3).

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.
@github-actions github-actions Bot added area/database Database engine behavior, schema issues, cross-engine DB bugs db/postgres PostgreSQL engine-specific issue labels Aug 19, 2026
@kolaente
kolaente enabled auto-merge (rebase) August 19, 2026 06:43
@github-actions

Copy link
Copy Markdown

Preview Deployment

Preview deployments for this PR are available at:

URL Tag Commit
https://pr-3554.preview.vikunja.dev ghcr.io/go-vikunja/vikunja:pr-3554 latest
https://sha-0ad0a5c82add892640bca21a341e0bd3d910e96c.preview.vikunja.dev ghcr.io/go-vikunja/vikunja:sha-0ad0a5c82add892640bca21a341e0bd3d910e96c 0ad0a5c

The preview environment will start automatically on first visit. Subsequent pushes to this PR will update the pr-3554 image — the preview picks up the new version on restart. The per-commit URLs point to a specific version and will not change.

Run locally with Docker
docker pull ghcr.io/go-vikunja/vikunja:pr-3554
docker run -p 3456:3456 ghcr.io/go-vikunja/vikunja:pr-3554

Last updated for commit 0ad0a5c

@kolaente
kolaente merged commit a1f0606 into main Aug 19, 2026
42 checks passed
@kolaente
kolaente deleted the paradedb-test-flakiness branch August 19, 2026 06:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/database Database engine behavior, schema issues, cross-engine DB bugs db/postgres PostgreSQL engine-specific issue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants