NUAAwqy opened a new issue, #5098: URL: https://github.com/apache/rocketmq-dashboard/issues/5098
- [x] I searched open issues and pull requests and did not find a duplicate. - [x] This is a RocketMQ Studio frontend defect. - [x] I reproduced it on the current `rocketmq-studio` branch. ### Studio Version - Branch: `rocketmq-studio` - Commit: `a562601d` - Built from source ### Runtime Environment - Browser time zone: any IANA zone with a spring-forward DST gap (reproduced with `America/New_York`) - Node.js: 24.11.1 (automated regression test) - Connected RocketMQ cluster: not required; the defect occurs before the request is sent ### Describe the Bug The one-time maintenance-window form converts `datetime-local` values with the JavaScript `Date` constructor. For a wall-clock time that does not exist during a spring-forward transition, JavaScript silently normalizes the input to a later time. Recurring maintenance windows already use the IANA-zone conversion utility, which rejects the same invalid input. ### Steps to Reproduce 1. Use a browser time zone with a DST spring-forward transition, such as `America/New_York`. 2. Open **System Alerts** -> **Maintenance windows**. 3. Choose a one-time window and enter `2026-03-08T02:30`. 4. Submit the form. ### What Did You Expect to See? The form should reject the nonexistent wall-clock time and avoid sending a shifted maintenance window. ### What Did You See Instead? The local `Date` conversion normalizes `02:30` to `03:30`, so the request can contain a maintenance window shifted by one hour. ### Additional Context The existing `zonedLocalDateTimeToUtc` helper already detects nonexistent local times. Reusing that conversion for browser-local one-time windows makes one-time and recurring behavior consistent. ### Are You Willing to Submit a Pull Request? - [x] Yes, I am willing to submit a pull request. -- 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]
