Wang1rrr opened a new issue, #6982: URL: https://github.com/apache/rocketmq-dashboard/issues/6982
### Describe the bug The HTTP streaming client gives response-body reading a fresh full `requestTimeout` after waiting for response headers. Since the JDK input-stream body handler completes the response once headers arrive, a slow provider can occupy the worker for almost twice the configured request timeout. ### Reproduction A local HTTP fixture delays headers by 600 ms, then delays a valid SSE completion by another 600 ms. With a one-second timeout, the current client returns successfully after about 1.2 seconds. The new regression fails before any production change (`streamTimeoutIncludesTimeSpentWaitingForHeadersTest`). ### Expected behavior Use one elapsed-time budget across waiting for headers and consuming the stream. When the remaining budget expires, retain the existing HTTP 504 / `llm.provider.timeout` result and close/cancel the body reader. -- 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]
