lokidundun commented on code in PR #7860:
URL: https://github.com/apache/incubator-seata/pull/7860#discussion_r2618004591


##########
changes/en-us/2.x.md:
##########
@@ -56,6 +56,7 @@ Add changes here for all PR submitted to the 2.x branch.
 - [[#7796](https://github.com/apache/incubator-seata/pull/7796)] fix the NPE 
on ConsulConfigurationTest method
 - [[#7839](https://github.com/apache/incubator-seata/pull/7839)] resolve 
TransactionAutoConfiguration compatibility with Spring Boot 4.x
 - [[#7855](https://github.com/apache/incubator-seata/pull/7855)] fix comma 
missing in package.json/min-document
+- [[#7351](https://github.com/apache/incubator-seata/issues/7351)] Fix the 
issue where delayed messages in RocketMQ transactions were silently ignored, 
now explicitly throwing an exception

Review Comment:
   This pr address is wrong, maybe it is 7860



##########
changes/en-us/2.x.md:
##########
@@ -137,6 +138,7 @@ Add changes here for all PR submitted to the 2.x branch.
 - [[#7808](https://github.com/apache/incubator-seata/pull/7808)] Deflake 
multiple Insert Executor tests by fixing order-dependent primary key (PK) value 
comparison
 - [[#7815](https://github.com/apache/incubator-seata/pull/7815)] test: fix 
combine test to avoid failure due to ordering
 - [[#7827](https://github.com/apache/incubator-seata/pull/7827)] Fix 
non-deteriministic in TableMetaTest#testGetPrimaryKeyOnlyName
+- [[#7351](https://github.com/apache/incubator-seata/issues/7351)] Add unit 
test for delayed message validation in RocketMQ transaction

Review Comment:
   This log maybe should be removed.



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