FE: fix invisible tool runs and reconnect gaps in tickets/mingo chat#33
Conversation
|
Warning Review limit reached
Next review available in: 49 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: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (11)
✨ 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 |
- Pair id-less EXECUTED chunks with the newest in-flight EXECUTING of the same (integratedToolType, toolFunction); scan newest-first so stale interrupted cards from earlier turns don't swallow the current run - updateToolExecutionInMessages now returns whether anything matched so callers append a fresh segment instead of silently dropping the event (the first post-MESSAGE_END EXECUTING chunk of an approved command) - Open a fallback assistant bubble when no assistant message exists yet instead of dropping segments; fix compaction upsert to replace the last 'started' segment (mirrors the lib's upsertTrailingCompaction) - Surface NATS reconnects from TicketDialogSubscription so the parent can refetch persisted history (CHAT_CHUNKS stream retains ~10 min) - Bump @flamingo-stack/openframe-frontend-core to ^0.0.448; refresh schema.graphql
df224e6 to
6e293df
Compare
Summary
EXECUTEDchunks now pair with the newest in-flightEXECUTINGof the same(integratedToolType, toolFunction); matching scans newest-first so a stale interrupted card from an earlier turn can't swallow the current run (ticketsticket-details-store+ mingomingo-messages-store).updateToolExecutionInMessagesreturns whether anything matched, so callers append a fresh segment instead of dropping the event — fixes the invisible tool run afterMESSAGE_ENDfor approved commands. When no assistant bubble exists yet (cleared thread / history not hydrated), a fallback bubble is opened.startedcompaction segment (mirrors the lib'supsertTrailingCompaction) — a second compaction landing in the same bubble is no longer dropped.TicketDialogSubscriptionsurfaces NATS reconnects viaonReconnectedso the parent refetches persisted history (theCHAT_CHUNKSstream retains ~10 min; longer outages leave a gap JetStream replay can't fill).@flamingo-stack/openframe-frontend-coreto^0.0.448; refreshschema.graphqlfrom introspection.Notes
Test plan