You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by GitBox <gi...@apache.org> on 2026/10/01 15:01:15 UTC
[GH] (rocketmq-dashboard/codex/user-deletion): Workflow run "CI" failed!
The GitHub Actions job "CI" on rocketmq-dashboard.git/codex/user-deletion has failed.
Run started by GitHub user tju-yxq (triggered by tju-yxq).
Head commit for run:
a6112e9966fff6fb0393ecafd76a55953c58ca0e / Yxq <30...@tju.edu.cn>
feat(auth): delete a studio user account and its sessions
The user management page can create and disable studio accounts but
never remove them, so offboarded accounts accumulate forever and their
usernames stay permanently reserved (createUser rejects any existing
name with 409 regardless of the old account's state).
Add DELETE /api/studio-users/{userId} backed by AuthService.deleteUser:
- the account row and its sessions are removed in one transaction (the
sessions table has no foreign key, so the rows would otherwise linger
as unreachable tokens);
- the operator's own account is rejected with 400 (disable it instead);
- the last enabled administrator is rejected with 409 under the same
FOR UPDATE row lock the disable path uses, so concurrent deletes of
the remaining admins cannot lock the deployment out;
- a disabled administrator can be deleted even when it is the only
admin account, because it is not part of the enabled-admin set.
The page adds a destructive Popconfirm on each row (disabled for the
current account) and reloads the list after a successful delete.
Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/36880045356
With regards,
GitHub Actions via GitBox