Loyal-Young opened a new issue, #6414: URL: https://github.com/apache/rocketmq-dashboard/issues/6414
### Before Creating the Bug Report - [x] Searched for duplicates. Searched silence/gap; #5896 fixes fall-back offsets and is already incorporated. This concerns an occurrence whose start itself lands inside a spring-forward gap. - [x] This concerns RocketMQ Studio. ### Studio Version rocketmq-studio, 779b8c0e7aed2396d3cc72743dcd544ea48e9ae6. ### Runtime Environment Windows; Java 21 / Node 24. Reproduction will use the real schedule/service or React hook with controlled dependencies. ### Connected RocketMQ Cluster No live broker is required for this defect. ### Describe the Bug AlertSilenceSchedule computes candidateEnd from candidateStart.toLocalDateTime(). candidateStart has already been moved through a DST gap by ZonedDateTime.ofLocal. The gap is consequently added to the end as well. For a New York daily window seeded at 02:30–04:00 on March 7, 2026, the March 8 start resolves to 03:30 but the end resolves to 05:00 rather than the configured 04:00. Alerts continue to be suppressed for an extra hour. ### Steps to Reproduce Create a daily America/New_York silence with startsAt=2026-03-07T07:30Z, endsAt=2026-03-07T09:00Z, recurrenceUntil after March 9. Evaluate March 8 at 08:15Z (04:15 EDT): it is incorrectly active until 09:00Z. ### What Did You Expect to See? Keep the existing start-gap resolution and seed-offset policy, but derive both occurrence endpoints from their scheduled wall-clock values so shifting the start cannot also move the end. Include a 30-minute DST gap and ordinary-day controls. ### Are You Willing to Submit a Pull Request? - [x] Yes, including regression and positive-path tests. -- 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]
