[fix] Point the watchdog collapse test at its own database - #6567
Conversation
Expose the fixture-generated database name to the concurrency test. Connect the raw sweep and observer clients to that isolated database. Claude-Session: https://claude.ai/code/session_0164kzT6ttwpBtzvcDC6YzYk
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. 🗂️ Base branches to auto review (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Team Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
Railway Preview Environment
Updated at 2026-09-05T09:13:46.147Z |
Context
test_c opened its raw sweep connections against the base database instead of the fixture-created database. This could pollute operator data and made the heartbeat wait time out. The fixture now exposes its generated database name, and the raw sweep and observer connections use it directly.
Tests
https://claude.ai/code/session_0164kzT6ttwpBtzvcDC6YzYk