fix(datetime): make sure the epoch is not larger than the maximum supported value #11424
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A user sets a large timestamp by API to the banned feature, the value of this timestamp is out of the supported range and will crash the list API of the banned feature, and meanwhile, there is no
clean_all
API in this feature, thus the user can't delete the bad date.There will be a series PRs to unify the
emqx_datetime
andemqx_calender
Fixes
Summary
🤖 Generated by Copilot at 526c61c
Export and implement
epoch_to_rfc3339
functions inemqx_calendar
module and improveemqx_datetime
module to handle maximum epoch timestamp. These changes are for better compatibility and validation of date and time formats.PR Checklist
Please convert it to a draft if any of the following conditions are not met. Reviewers may skip over until all the items are checked:
changes/(ce|ee)/(feat|perf|fix)-<PR-id>.en.md
filesChecklist for CI (.github/workflows) changes
changes/
dir for user-facing artifacts update