I will first open by explaining why I discovered this. See here. A user was posting content totally unrelated to Voat to /v/Voat, and I tried to explain this three times without ever receiving a response. I suspect that the user does not check notifications and does not realize what he or she has been doing by posting random political content to /v/Voat. After three warnings, I decided I would temporarily ban the user from /v/Voat, in the hope that, through the user ban message, I could get my point across that I have clearly not been getting across via submission replies.
When attempting to do this, however, I discovered two bugs associated with user banning.
1) There is a 500 character limit to user ban messages, and if the message exceeds 500 characters, the following error message is displayed (even before hitting "Add"):
The field Description must be a string with a maximum length of 500.
And the same message is displayed again above if the "Add" button is clicked.
This is all expected behaviour. However, if the message is reduced to 500 characters, while the warning goes away beneath the message box, attempting to click "Add" will yield a new message above:
And this error will be displayed until the user ban message is reduced to 439 characters or fewer. 440 characters will still trigger the error and prevent the ban from being added.
2) After noticing this bug, I began testing, and in the testing process I once accidentally forgot to select a Rule. Hitting "Add" with a username entered, but no Rule selected, as per this, yields this result. The error message is fine, but notice that the subverse-specific Rules have been replaced with the message "No rules found", which is the standard message presented when subverses do not have any subverse-specific Rules.
So those are the two BUGs I discovered associated with user banning.