fix(hermes/marmot): accept is_reconnect kwarg in connect()#839
Conversation
|
Ready to review this PR? Stage has broken it down into 2 individual chapters for you:
Chapters generated by Stage for commit 9b8a06d on Jul 17, 2026 2:20am UTC. |
|
Warning Review limit reached
Next review available in: 38 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
WalkthroughThe Marmot adapter’s ChangesMarmot connection compatibility
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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. Comment |
The hermes-agent gateway connects adapters via connect(is_reconnect=...) on cold boot and reconnect alike, so the override must accept the keyword-only argument even though wn-agent owns reconnect/resync and the flag is intentionally unused. Includes a regression test pinning the gateway calling convention against both the adapter and the base-class test stub. Closes marmot-protocol#836 Co-authored-by: Javier G. Montoya S <jgmontoya@pm.me>
8726d80 to
9b8a06d
Compare
Fixes #836.
hermes-agentconnects platform adapters viaawait adapter.connect(is_reconnect=...), and the base adapter plus the bundled SimpleX plugin both use the keyword-only signatureasync def connect(self, *, is_reconnect: bool = False) -> bool. The Marmot adapter's override wasasync def connect(self), so every connect raised:and the platform never came up (no socket opened to
wn-agent).This widens the signature to match; the body doesn't need the argument. One line.
Verified on a live deployment: after this change the adapter connects and the platform reaches
connected.Summary by CodeRabbit