pilichoumao opened a new issue, #6636: URL: https://github.com/apache/rocketmq-dashboard/issues/6636
### Before Creating the Bug Report - [x] Searched existing issues and pull requests; no equivalent open-ended system-alert filter fix found. - [x] This concerns RocketMQ Studio in this repository. - [x] Reproduced on the current rocketmq-studio revision. ### Studio Version `rocketmq-studio` at `e2f815fba774a1e399bf9bb3709246edca1a436d` (includes #6633). ### Runtime Environment Ubuntu 24.04 ECS, Node.js 20.20.2, Vitest/jsdom, Asia/Shanghai. The actual RangePicker is rendered; only the service is mocked. ### Connected RocketMQ Cluster Not needed to reproduce this frontend request-construction defect. ### Describe the Bug #6633 replaced two independent datetime inputs with a RangePicker. Without allowEmpty, a start-only or end-only selection is not committed, so the page keeps making an unrestricted time query. Previously the inputs could set either endpoint independently, and the backend still accepts from/to independently. ### Steps to Reproduce 1. Open system alerts and enter only the start time (or only the end time). 2. Confirm the date and leave the picker. 3. Observe that the alert-list request still has no corresponding time boundary. ### Expected Behavior Start-only filtering submits from with no to; end-only filtering submits to with no from, using the existing local-to-UTC conversion. A bounded range continues to work. ### Actual Behavior Both single-boundary regressions fail on the current component. The existing bounded-range test passes. An isolated prototype enabling allowEmpty passes both regressions and all 23 page tests (21 existing plus 2 research cases). ### Additional Context The minimal fix preserves the single RangePicker layout and existing API, conversion, pagination reset and export query handling. Regressions should exercise the picker and service arguments, including export using each single boundary. No new UI text is needed. ### Are You Willing to Submit a Pull Request? - [x] Yes. -- 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]
