mochi-mqtt / server

99%

main: 99%

LAST BUILD ON BRANCH maintainers/mochi-co/file-based-config

branch: maintainers/mochi-co/file-based-config

CHANGE BRANCH

x

Reset

Sync Branches

• maintainers/mochi-co/file-based-config
• update-imports
• master
• refs/tags/v2.3.0
• main
• fix-readme-example
• mochi-co/inline-subscriptions
• small-fixes-cleanups
• refs/tags/v2.4.0
• wait-for-all-clients-to-disconnect-before-continuing
• mochi-co-patch-1
• recommended-minimum-keepalive
• refs/tags/v2.4.1
• dependabot/go_modules/golang.org/x/net-0.17.0
• remove-vendor-folder
• revert-321-main
• refs/tags/v2.4.2
• refs/tags/v2.4.3
• refs/tags/v2.4.4
• file-based-config
• refs/tags/v2.4.5
• refs/tags/v2.4.6
• dependabot/go_modules/google.golang.org/protobuf-1.33.0
• refs/tags/v2.6.0
• refs/tags/2.6.0
• refs/tags/v2.6.1
• refs/tags/v2.6.2
• dependabot/go_modules/golang.org/x/net-0.23.0
• refs/tags/v2.6.3
• refs/tags/v2.6.4
• refs/tags/v2.6.5
• refs/tags/v2.6.6

Build # 6597314012

Build Type

push

github

Committed by web-flow

Commit Message

Fix for unlimited maximum message expiry interval (#315)

* fix when no max msg expiry interval is set

* fix expiry handling of clearExpiredInflights

* Modify it to handle cases where the MaximumMessageExpiryInterval is set to 0 or math.MaxInt64 for no expiry, and optimize some of the code and test cases.

* Set MaximumMessageExpiryInterval to 0 or math.MaxInt64 for no expiration, and optimize some of the code and test cases.

* Addressing the issue of numeric overflow with expiration values.

* Only when server.Options.Capabilities.MaximumMessageExpiryInterval is set to math.MaxInt64 for no expiry.

* fix typo in README.md

* There is no need to verify whether 'maximumExpiry' is 'math.MaxInt64' within 'client.ClearInflight()

* Optimize the code to make it easier to understand.

* Differentiate the handling of 'expire' in MQTTv5 and MQTTv3; skip expiration checks if MaximumMessageExpiryInterval is set to 0; optimize code and test cases.

* When MaximumMessageExpiryInterval is set to 0, it should not affect the message's own expiration(for v5) evaluation.

* Adding client.ClearExpiredInflights() to clear expired messages, while client.ClearInflights() is used to clear all inflight messages.

---------

Co-authored-by: JB <28275108+mochi-co@users.noreply.github.com>
Co-authored-by: werben <werben@aliyun.com>
Co-authored-by: werben <werben@qq.com>

Run Details

26 of 26 new or added lines in 2 files covered. (100.0%)

5447 of 5515 relevant lines covered (98.77%)

64.62 hits per line