mirror of
https://gitee.com/mateos/mateclaw.git
synced 2026-09-13 11:13:43 +08:00
Same bug as the prior queue-drop fix in doOnComplete, but in the sister branch that fires when the agent's reactive stream errors out (CancellationException from a user stop). The guard cr.queuedInput() != null && !(isUserStop && !isInterruptFollowup) mis-classified "user stopped, no interrupt-with-followup, but a message is in the queue" as an explicit abort and silently dropped the freshly-typed follow-up. The frontend's enqueue path never sets interruptType — it just calls requestStop + offers to messageQueue. Whoever puts a message in the queue means it; just run it. Aligns with doOnComplete and the four other queue-launch sites in this controller. |
||
|---|---|---|
| .. | ||
| src | ||
| Dockerfile | ||
| pom.xml | ||
| settings.xml | ||