feat(postgresql): wire binary catalog integration#41
Conversation
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (10)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Review rate limit: 0/1 reviews remaining, refill in 34 minutes and 33 seconds.Comment |
Adds PostgreSQL to the daemon's active binary catalog fallback and related integration surfaces: CLI catalog summary, settings port persistence, firewall port registration, service icon mapping, and coverage for catalog fallback/Core catalog expectations.\n\nLocal verification:\n- dotnet test tests/NKS.WebDevConsole.Daemon.Tests/NKS.WebDevConsole.Daemon.Tests.csproj -c Debug --filter FullyQualifiedName
CatalogClientTests --nologo\n- dotnet test tests/NKS.WebDevConsole.Core.Tests/NKS.WebDevConsole.Core.Tests.csproj -c Debug --filter FullyQualifiedNameBinaryCatalogTests --nologo\n- npm run type-check\n- dotnet build WebDevConsole.sln -c Debug --nologo\n- npm run build\n- node scripts/e2e-isolated-lifecycle.mjs --priority P0