Alanxtl opened a new issue, #3820: URL: https://github.com/apache/dubbo-go/issues/3820
Part of #3614 (item 5). ### What happened? The original report contains a race in `github.com/apache/dubbo-getty v1.4.10`: session shutdown reads timeout state while the TCP connection updates a read deadline. The dependency is still pinned to v1.4.10 at `develop` revision `6ea4f0817299973c5e17e73fea3710cf528c1426`. **Current reproduction status:** on Windows with Go 1.26.3, ten isolated runs of `TestDubboProtocol_Refer` and one full `protocol/dubbo` package run passed under `-race`. This does not establish whether the originally reported race has been fixed; please investigate using the original logs and a suitable stress reproducer. One point to investigate is that `gettyConn.ReadTimeout` has a value receiver and therefore copies a connection containing atomic fields. This is a hypothesis to verify, not a confirmed root cause. apache/dubbo-getty#145 describes related TCP session shutdown races; they are not necessarily the same race. ### Reproduction Original race logs and environment are linked from #3614. A starting point is: ```sh go test -race -count=10 ./protocol/dubbo -run '^TestDubboProtocol_Refer$' ``` ### Expected outcome - Determine whether the exact reported race is still reachable and document a reliable reproducer or evidence that it is resolved. - If confirmed, fix it in the appropriate repository, update the dependency in dubbo-go if needed, and add regression coverage. - Remove the test from `RACE_SKIP_TESTS` only after the original scenario is verified race-free. -- 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]
