phacility/phabricator · error · PhutilArgumentUsageException
Specify %s to reset all action counters.
Error message
Specify %s to reset all action counters.
What it means
Thrown by `bin/auth unlimit` when `--all` is not passed. The workflow currently only supports resetting every action counter for the chosen user, and requires `--all` explicitly (per the in-code TODO) so that the command's semantics stay stable when more tailored resets are added later. It is a usage guard, not a runtime failure.
Source
Thrown at src/applications/auth/management/PhabricatorAuthManagementUnlimitWorkflow.php:52
}
$user = id(new PhabricatorPeopleQuery())
->setViewer($this->getViewer())
->withUsernames(array($username))
->executeOne();
if (!$user) {
throw new PhutilArgumentUsageException(
pht(
'No user exists with username "%s".',
$username));
}
$all = $args->getArg('all');
if (!$all) {
// TODO: Eventually, let users reset specific actions. For now, we
// require `--all` so that usage won't change when you can reset in a
// more tailored way.
throw new PhutilArgumentUsageException(
pht(
'Specify %s to reset all action counters.', '--all'));
}
$count = PhabricatorSystemActionEngine::resetActions(
array(
$user->getPHID(),
));
echo pht('Reset %s action(s).', new PhutilNumber($count))."\n";
return 0;
}
}
View on GitHub (pinned to 5720a38cfe)
Solutions
- Add the required flag: `bin/auth unlimit --user <username> --all`.
- Consult `bin/auth help unlimit` for the exact flag names before scripting.
- If you meant to reset only specific actions, note that is not yet supported — `--all` is the only mode.
Example fix
// before $ bin/auth unlimit --user alice Specify --all to reset all action counters. // after $ bin/auth unlimit --user alice --all
Defensive patterns
Strategy: validation
Prevention
- Remember `--all` is mandatory by design; there is no narrower reset yet.
- Pin the full command (`bin/auth unlimit --user X --all`) in scripts and runbooks so the flag is never omitted.
- Check `bin/auth help unlimit` after Phabricator upgrades in case flags change.
When it happens
Trigger: Running `bin/auth unlimit --user alice` without `--all`; passing a misspelled flag such as `--everything` or `-a` which PhutilArgumentParser does not bind to the 'all' argument.
Common situations: The admin expects `--user` alone to be sufficient; older internal runbooks document the pre-`--all` invocation; script uses a short flag that the parser silently treats as unknown.
Related errors
- Use %s to choose a user to reset actions for.
- Specify an OAuth client ID with %s.
- You must specify the email to verify.
- Request parameter "%s" is not formatted properly. Expected a
- Specify a public key to revoke trust for with --id.
AI-assisted analysis of phacility/phabricator@5720a38cfe (2026-08-21).
Data as JSON: /api/errors/2ab3d0d44ae08c47.
Report an issue: GitHub.