feat(a2a-nats): add client message_stream per-operation method - #340
Conversation
yordis
commented
Jun 19, 2026
- Per-op slice of the client handle: message/stream pairs the bootstrap unary call with a JetStream subscription, and threading the prefix + req_id + consumer config by hand at every call site is the kind of footgun the handle exists to hide.
Streaming responses need both the bootstrap RPC and the JetStream subscription wired together on the agent's per-task event subject; combining them on the handle keeps callers from threading the prefix + req_id + consumer config by hand for every stream. Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
PR SummaryMedium Risk Overview The method uses Tests cover default agent subject, gateway-routed subject, and transport error propagation, consistent with existing per-operation handle tests. Reviewed by Cursor Bugbot for commit 031bd76. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughAdds ChangesA2aClient JetStream Streaming Operation
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 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 |
Code Coverage SummaryDetailsDiff against mainResults for commit: 031bd76 Minimum allowed coverage is ♻️ This comment has been updated with latest results |