Skip to content

Conversation

@yx9o
Copy link
Contributor

@yx9o yx9o commented Dec 13, 2025

Fixes #9923 .

@codecov-commenter
Copy link

codecov-commenter commented Dec 13, 2025

Codecov Report

❌ Patch coverage is 50.00000% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 48.79%. Comparing base (beee84f) to head (1cf8904).
⚠️ Report is 2 commits behind head on develop.

Files with missing lines Patch % Lines
...mq/client/impl/producer/DefaultMQProducerImpl.java 50.00% 1 Missing and 3 partials ⚠️
Additional details and impacted files
@@              Coverage Diff              @@
##             develop    #9924      +/-   ##
=============================================
- Coverage      48.91%   48.79%   -0.12%     
+ Complexity     12770    12736      -34     
=============================================
  Files           1324     1324              
  Lines          96288    96297       +9     
  Branches       12409    12411       +2     
=============================================
- Hits           47097    46989     -108     
- Misses         43458    43554      +96     
- Partials        5733     5754      +21     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

MessageAccessor.clearProperty(msg, MessageConst.PROPERTY_DELAY_TIME_LEVEL);
}
if (msg.getDelayTimeMs() != 0) {
MessageAccessor.clearProperty(msg, MessageConst.PROPERTY_TIMER_DELAY_MS);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In this situation, it is recommended to throw an exception directly, so that the user can perceive the usage error.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've thought about that too. Currently, the processing is consistent with the existing level. But if an exception is thrown, will there be semantic differences after the user upgrades?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Enhancement] Transactional messages should not send custom delayed messages

4 participants