fix(db): check if db is running when executing migrations

[paulo]

Summary

Follow-up to #7994

Now, if a DB is already running, instead of starting a new DB on a separate process, we try to connect to the existing one.

[github-actions]

📊 Benchmark results

Comparing with e7ef7f8

• Dependency count: 1,083 (no change)
• Package size: 352 MB (no change)
• Number of ts-expect-error directives: 362 (no change)

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a6527700-c082-4c06-8894-f0b899ae4edd

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch pa/fix-running-db

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}