Issue 1712 in reviewboard: Increase auth_user.username field size and allow '@' in user names

Status: New Owner: Labels: Type-Enhancement Priority-Medium New issue 1712 by ricklei: Increase auth_user.username field size and allow '@' in user names http://code.google.com/p/reviewboard/issues/detail?id=1712 *NOTE: If you have a patch, please submit it to

Re: Issue 1712 in reviewboard: Increase auth_user.username field size and allow '@' in user names

Comment #1 on issue 1712 by chipx86: Increase auth_user.username field size and allow '@' in user names http://code.google.com/p/reviewboard/issues/detail?id=1712 Unfortunately, these are restrictions put in place by Django, and not something we have a lot of control over. At least, the

Re: Issue 1712 in reviewboard: Increase auth_user.username field size and allow '@' in user names

Comment #2 on issue 1712 by ricklei: Increase auth_user.username field size and allow '@' in user names http://code.google.com/p/reviewboard/issues/detail?id=1712 A one byte patch to accounts/admin.py would fix the '@' issue: --- accounts/admin.py 2010-07-06 13:09:40.0 +0800 +++

Issue 1713 in reviewboard: postreview.py fails with API Error 105

Status: New Owner: Labels: Type-Defect Priority-Medium New issue 1713 by daniel.shiryu: postreview.py fails with API Error 105 http://code.google.com/p/reviewboard/issues/detail?id=1713 We use the pre-commit-hook from this review: http://reviews.reviewboard.org/r/822/ It uses the

Re: Issue 1713 in reviewboard: postreview.py fails with API Error 105

Comment #1 on issue 1713 by chipx86: postreview.py fails with API Error 105 http://code.google.com/p/reviewboard/issues/detail?id=1713 Neither. It looks like you didn't run 'rb-site upgrade' on your site, so there are fields missing from your database. -- You received this message because