pilichoumao opened a new pull request, #6392: URL: https://github.com/apache/rocketmq-dashboard/pull/6392
Fixes #6324. Once 64 stdio calls are outstanding, the next stdin event blocks the proxy in `handleEvent` while acquiring a slot. The main loop then stops forwarding server notifications until a call completes. This delays progress from already running calls; it is not a claim of permanent deadlock. Defer stdin consumption at the existing call limit while continuing to process notifications, results and cancellation. No concurrency/buffer increase, handshake/reconnect change or request replay. Document the scheduling behavior. Validation on current rocketmq-studio `779b8c0e7aed2396d3cc72743dcd544ea48e9ae6` (updated from the initial `5e4c39b0` base): - The real initialize/initialized + HTTP POST SSE regression fails on the current unmodified base: progress remains blocked with 64 calls outstanding. A reader EOF checkpoint and a separate server response gate establish the queued-input scenario without the exploration's fixed sleep. - After the fix, progress is forwarded before releasing calls, all 66 requests drain, all 67 response frames including initialize are received, and measured peak outstanding HTTP calls remains 64. - Focused saturation/cancellation tests passed 10 race runs on the initial base; current full `go test -race -count=1 -parallel 1 -timeout 60s ./...` passes after rebasing. Existing handshake, notification drain and cancellation controls remain passing. - Current `make fmt vet build-all` passes, including catalog consistency, six platform builds and license manifests. - A disposable composition with #6317's actual stdout-failure/cleanup implementation and tests passes the entire cmd package with race detection. None of #6317's changes are included here; it addresses a separate output failure boundary. All builds/tests ran sequentially with `GOMAXPROCS=1`, `GOMEMLIMIT=384MiB`, `GOFLAGS=-p=1`. The fixed set of small concurrent calls tests the existing limit; all contexts/sessions/server gates/workers are cleaned up, with no live broker/database or background service. AI-assisted implementation; reviewed the final diff and raw evidence. Overall remote CI remains to be observed. -- 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]
