funky-eyes commented on code in PR #7683:
URL: https://github.com/apache/incubator-seata/pull/7683#discussion_r2418330609


##########
changes/zh-cn/2.x.md:
##########
@@ -44,6 +44,7 @@
 - [[#7624](https://github.com/apache/incubator-seata/pull/7624)] 
修复yml配置文件中对于整数的兼容问题
 - [[#7644](https://github.com/apache/incubator-seata/pull/7644)] 
修复JAVA25时spotless的兼容性问题
 - [[#7662](https://github.com/apache/incubator-seata/pull/7662)] 确保 rm 的可见性,并且 
MockTest 中的方法按顺序执行
+- [[#7682](https://github.com/apache/incubator-seata/pull/7682)] 重写 
XABranchXid的equals和hashCode,解决mysql driver内存泄漏问题

Review Comment:
   ```suggestion
   - [[#7683](https://github.com/apache/incubator-seata/pull/7683)] 重写 
XABranchXid的equals和hashCode,解决mysql driver内存泄漏问题
   ```



##########
changes/en-us/2.x.md:
##########
@@ -44,6 +44,7 @@ Add changes here for all PR submitted to the 2.x branch.
 - [[#7624](https://github.com/apache/incubator-seata/pull/7624)] fix the 
compatibility issue of yml configuration files
 - [[#7644](https://github.com/apache/incubator-seata/pull/7644)] fix the 
compatibility issue of spotless when java 25
 - [[#7662](https://github.com/apache/incubator-seata/pull/7662)] ensure 
visibility of rm and The methods in MockTest are executed in order
+- [[#7682](https://github.com/apache/incubator-seata/pull/7682)] Override 
XABranchXid equals() and hashCode() to fix memory leak in mysql driver

Review Comment:
   ```suggestion
   - [[#7683](https://github.com/apache/incubator-seata/pull/7683)] Override 
XABranchXid equals() and hashCode() to fix memory leak in mysql driver
   ```



-- 
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]

Reply via email to