The GitHub Actions job "CI" on rocketmq-dashboard.git/codex/certs-delete-guard has failed. Run started by GitHub user tju-yxq (triggered by tju-yxq).
Head commit for run: 2066ccd7e9451f4e6905e39c9be01aa4252ed65d / Yxq <[email protected]> fix(web): keep concurrent certificate deletes independent The K8s certificate page tracked the in-flight delete in a single deletingId slot with no entry guard: deleting a second certificate while the first request was running overwrote the slot, so the first row's spinner vanished and its delete button became clickable again mid-request, and the first handler's finally then cleared the second row's spinner as well. Re-clicking the re-enabled row re-POSTed deleteK8sCert for a certificate that was already deleted, surfacing a spurious error toast for a delete that had succeeded. Track in-flight deletes in a per-id Set behind a synchronous ref guard (the repo's row-action idiom, e.g. AlertRuleAssetList's exportingNames), so concurrent deletes keep independent spinners and a repeated confirmation for the same row is a no-op. Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/37025124767 With regards, GitHub Actions via GitBox
