Add account, step 2, with the token box left empty: the wizard shows the engine's raw argument error, "The value cannot be an empty string or composed entirely of whitespace. (Parameter 'token')", and the activity log records "token rejected" although no token was sent anywhere.
Seen in the owner's log on a 1.1.1-dev build.
Wanted
The wizard says "Enter a token to continue." and asks nothing of the server. The cases that already have their own message (the default token is gone; an edited account has no stored token) stay as they are.
## What happens
Add account, step 2, with the token box left empty: the wizard shows the engine's raw argument error, "The value cannot be an empty string or composed entirely of whitespace. (Parameter 'token')", and the activity log records "token rejected" although no token was sent anywhere.
Seen in the owner's log on a 1.1.1-dev build.
## Wanted
The wizard says "Enter a token to continue." and asks nothing of the server. The cases that already have their own message (the default token is gone; an edited account has no stored token) stay as they are.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What happens
Add account, step 2, with the token box left empty: the wizard shows the engine's raw argument error, "The value cannot be an empty string or composed entirely of whitespace. (Parameter 'token')", and the activity log records "token rejected" although no token was sent anywhere.
Seen in the owner's log on a 1.1.1-dev build.
Wanted
The wizard says "Enter a token to continue." and asks nothing of the server. The cases that already have their own message (the default token is gone; an edited account has no stored token) stay as they are.