bigbigbigwaterbucket opened a new pull request, #1085: URL: https://github.com/apache/incubator-seata-go/pull/1085
<!-- Thanks for sending a pull request! --> <!-- Please make sure you have read and understood the contributing guidelines --> - [ ] I have registered the PR [changes](https://github.com/apache/incubator-seata-go/tree/master/changes). **What this PR does**: - add a cache-drain cleanup path for TCC Fence when pushCleanChannel falls back to logCache under queue pressure - add a stop signal so the drain goroutine exits cleanly on handler destroy - add regression tests for cache fallback and drain task behavior **Which issue(s) this PR fixes**: TCC Fence cleanup may leave stale fence log identities in logCache under queue pressure, leading to missed cleanup. Fixes #1084 <!-- *Automatically closes linked issue when PR is merged. Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`. _If PR is about `failing-tests or flakes`, please post the related issues/tests in a comment and do not use `Fixes`_* --> **Special notes for your reviewer**: The change follows the existing cleanup design and keeps the queue/cache model intact. It adds a minimal background drain path for cached identities and a stop signal for safer lifecycle handling, without altering TCC business semantics. **Does this PR introduce a user-facing change?**: <!-- If no, just write "NONE" in the release-note block below. If yes, a release note is required: Enter your extended release note in the block below. If the PR requires additional action from users switching to the new release, include the string "action required". --> ```release-note NONE ``` -- 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]
