The GitHub Actions job "CI" on rocketmq-dashboard.git/fix/rule-threshold-unavailable-toggle has failed. Run started by GitHub user Frun1na (triggered by Frun1na).
Head commit for run: dff750be240e44dbeed0df29bb21bc48b5fba561 / Apulupie <[email protected]> fix(ops): stop the Unavailable condition from erasing the rule threshold The condition select rewrote the threshold field with 0 whenever Unavailable was picked and never put the value back, so a rule the user was building as "> 1" was saved as "> 0" — on an availability metric (0/1) that fires on every available sample, and "< 0" never fires. The same zero also survived when the metric was switched to one without the condition, because that path resets the operator on its own. The write never reached the request: while the operator is Unavailable the threshold input is not rendered, form.validateFields() returns no threshold key, and the server stores 0 for the rule anyway. Removing it keeps every payload and stored value unchanged. Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/38792264835 With regards, GitHub Actions via GitBox
