Skip to content

Ditch PGLite database - #224

Closed
Arcticae wants to merge 1 commit into
apibara:mainfrom
software-mansion-labs:arcticae/ditch-pglite
Closed

Arcticae wants to merge 1 commit into
apibara:mainfrom
software-mansion-labs:arcticae/ditch-pglite

Conversation

@Arcticae

@Arcticae Arcticae commented Aug 5, 2026

Copy link
Copy Markdown

It seems to fail some workflows and be flaky, but let's see if it's a big problem going forward.
If not, this PR can be merged (env is in place) and we can see if it works better.

@coderabbitai

coderabbitai Bot commented Aug 5, 2026 •

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

@Arcticae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 53 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 28d0c70a-5801-44b9-9927-18451a45a849

📥 Commits

Reviewing files that changed from the base of the PR and between 0993bbf and f375da6.

📒 Files selected for processing (6)
  • .github/workflows/build.yml
  • packages/plugin-drizzle/tests/helper.ts
  • packages/plugin-drizzle/tests/persistence.test.ts
  • packages/plugin-drizzle/tests/reorg.test.ts
  • packages/plugin-drizzle/tests/storage.test.ts
  • turbo.json
📝 Walkthrough

Walkthrough

The Drizzle test helper now supports PGlite and isolated PostgreSQL databases. Tests use the renamed getTestDb factory. CI passes PostgreSQL and Sepolia configuration and runs pull request workflows for all branches.

Changes

Drizzle test database support

Layer / File(s) Summary
Configurable database factory
packages/plugin-drizzle/tests/helper.ts
getTestDb selects PGlite by default or PostgreSQL when TEST_POSTGRES_CONNECTION_STRING is set. PostgreSQL databases receive migrations and cleanup.
Test suite migration
packages/plugin-drizzle/tests/persistence.test.ts, packages/plugin-drizzle/tests/reorg.test.ts, packages/plugin-drizzle/tests/storage.test.ts
Persistence, reorganization, and storage tests now use getTestDb. Test scenarios and assertions remain unchanged.
CI test environment wiring
.github/workflows/build.yml, turbo.json
Pull request workflows run for all branches. CI passes Sepolia RPC and PostgreSQL connection variables to tests.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Possibly related PRs

Poem

A rabbit hops through tests anew,
With PGlite skies or Postgres blue.
Each database gets a careful name,
Then cleanup closes every frame.
CI runs branches far and wide—
Sepolia secrets tucked inside.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the main change: replacing PGlite with PostgreSQL to address flaky workflows.
Description check ✅ Passed The description explains that the change addresses workflow failures and flakiness and evaluates the new database setup.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@Arcticae
Arcticae force-pushed the arcticae/ditch-pglite branch from 4d3ce2a to f375da6 Compare August 5, 2026 13:31
@Arcticae Arcticae closed this Aug 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant