Conversation
…d output helpful error messages
|
WalkthroughA private method Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20–25 minutes
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🧰 Additional context used📓 Path-based instructions (3)**/*.{ts,tsx}📄 CodeRabbit inference engine (.github/copilot-instructions.md)
Files:
**/*.{ts,tsx,js,jsx}📄 CodeRabbit inference engine (.github/copilot-instructions.md)
Files:
**/*.{js,ts,jsx,tsx,json,md,css,scss}📄 CodeRabbit inference engine (AGENTS.md)
Files:
🧬 Code graph analysis (1)internal-packages/replication/src/client.ts (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (23)
🔇 Additional comments (3)
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 |
Add validation for logical replication publication configuration. Helps diagnose an issue where runs are no longer replicated to clickhouse because of a configuration issue with the replication publication.
Problem
The
LogicalReplicationClientonly checked if a publication existed, not if it was correctly configured. This caused a silent failure where:This happened when a publication existed but:
delete)Solution
Added
#validatePublicationConfiguration()method that validates:When validation fails, error messages include the exact SQL command to fix the issue:
Missing table:
Missing actions:
This prevents silent data loss and makes debugging configuration issues much easier.