Loyal-Young opened a new issue, #6436: URL: https://github.com/apache/rocketmq-dashboard/issues/6436
### What happened AlertRuleDuration accepts `9223372036854775807s`: it is a valid, representable Duration. AlertStateMachine then evaluates it by adding it to firstPendingAt or lastNotifiedAt. Both paths throw during Instant addition, interrupting the rule evaluation instead of keeping the alert pending or suppressing an early reminder. ### Reproduction At an ordinary current Instant, advance a matching initial state with required duration parsed from the value above. Separately, advance a FIRING state with the same reminder interval and lastNotifiedAt set. Both raise an overflow exception on rocketmq-studio 779b8c0. ### Proposed correction Compare elapsed Duration against the configured Duration without constructing an out-of-range deadline. Cover both branches, exact elapsed boundaries and clock rollback. This differs from #2649/#2818, which reject durations that cannot be represented by Duration itself; this input passes that parser correctly. -- 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]
