Aias00 opened a new issue, #7041: URL: https://github.com/apache/rocketmq-dashboard/issues/7041
## Evidence rocketmq-studio c34535db0 executes enhancement and final generation sequentially. Each HTTP call has its own 120-second budget, but the observing emitter lasts 125 seconds. Two 90-second calls fit their individual limits but exceed the observer lifetime. CLI enhancement and final generation likewise each receive a full budget; resume recovery can add another attempt. #6983 addresses headers/body within one HTTP request, not this whole-run boundary. ## Design and implementation Enforce one run-level wall-clock deadline across enhancement, generation and recovery, using the existing cancellation handle and TIMEOUT reason. Reserve time for stop grace and terminal persistence before the SSE observer expires. Cancel the deadline task at finalization, preserve a success already projected and user Stop precedence, and do not start generation/retry after cancellation. Existing individual provider timeouts remain additional safeguards. Add deterministic timer/cancellation tests plus a short-budget real worker test. No new dependencies or wire fields. ## Validation Java21 conversation/provider tests and Checkstyle; verify deadline cleanup, no next-stage invocation after expiry, one terminal frame, and correct TIMEOUT classification. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
