Alanxtl opened a new issue, #3458: URL: https://github.com/apache/dubbo-go/issues/3458
### Background Dubbo-go Triple keeps a forked/modified runtime derived from connect-go under `protocol/triple/triple_protocol`. Upstream connect-go fixed a concurrency bug in v1.19.2: `Fix nil pointer deref in duplexHTTPCall under concurrent Send + CloseAndReceive` (connectrpc/connect-go#919). Our local Triple runtime also has `duplexHTTPCall` and client stream APIs where `Send`, `CloseRequest`, `CloseResponse`, `ResponseHeader`, and `ResponseTrailer` may be used around the same stream lifecycle. This should be checked against the upstream fix instead of doing a broad connect-go upgrade. ### Scope - Inspect `protocol/triple/triple_protocol/duplex_http_call.go` for the same concurrent `Send` + close/receive race. - Add a focused regression test that exercises concurrent send and close/receive behavior for Triple client streams. - Port only the relevant synchronization/lifecycle fix if the race is reproducible or structurally possible. ### Notes This is not a request to adopt unrelated connect-go features such as HTTP GET, transport retry, or new codegen flags. The goal is only to align the runtime safety fix that matters for Dubbo-go Triple streaming. Reference: https://github.com/connectrpc/connect-go/releases/tag/v1.19.2 -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
