Re: Formatting errors in description field
Sorry for the late answer - I did not get any notification :/ Am Donnerstag, 17. Juli 2014 22:30:38 UTC+2 schrieb David Trowbridge: Can you show what the source markdown looks like? (Click the pencil and then copy/paste/redact) -David On Thu, Jul 17, 2014 at 2:34 AM, Philip Schiffer philip@sprylab.com javascript: wrote: Hello everyone, I have upgraded our reviewboard installation from 1.7.x to 2.0.3. Unfortunately we have some issues with the formatting of the description field. We are using the post-review tool in our scripts to post our reviews. Inside the description field we put the git commit log entries. As you can see in the attachment, there are problems displaying the links. I've searched the bug tracker but unfortunately I'm getting http 500 errors from google code for this issue: https://code.google.com/p/reviewboard/issues/detail?id=3377 -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Error 500 when posting comments
Hi all,
After a reboot of my reviewboard server, I am now getting Error 500
internal server errors any time a user tries to submit a comment on a
review request. I have verified that I can add new review requests, and
perform other edits on those review requests. Here is a sample error:
Traceback (most recent call last):
File
/usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/core/handlers/base.py,
line 112, in get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File
/usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/views/decorators/cache.py,
line 52, in _wrapped_view_func
response = view_func(request, *args, **kwargs)
File
/usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/views/decorators/vary.py,
line 19, in inner_func
response = func(*args, **kwargs)
File
/usr/lib/python2.6/site-packages/Djblets-0.8.7-py2.6.egg/djblets/webapi/resources.py,
line 494, in __call__
request, method, view, api_format=api_format, *args, **kwargs)
File
/usr/lib/python2.6/site-packages/Djblets-0.8.7-py2.6.egg/djblets/webapi/resources.py,
line 565, in call_method_view
return view(request, *args, **kwargs)
File
/usr/lib/python2.6/site-packages/Djblets-0.8.7-py2.6.egg/djblets/webapi/resources.py,
line 747, in post
return self.create(*args, **kwargs)
File
/usr/lib/python2.6/site-packages/Djblets-0.8.7-py2.6.egg/djblets/webapi/decorators.py,
line 117, in _call
return view_func(*args, **kwargs)
File
/usr/lib/python2.6/site-packages/ReviewBoard-2.0.4-py2.6.egg/reviewboard/webapi/decorators.py,
line 110, in _check
return view_func(*args, **kwargs)
File
/usr/lib/python2.6/site-packages/Djblets-0.8.7-py2.6.egg/djblets/webapi/decorators.py,
line 117, in _call
return view_func(*args, **kwargs)
File
/usr/lib/python2.6/site-packages/Djblets-0.8.7-py2.6.egg/djblets/webapi/decorators.py,
line 138, in _checklogin
return view_func(*args, **kwargs)
File
/usr/lib/python2.6/site-packages/Djblets-0.8.7-py2.6.egg/djblets/webapi/decorators.py,
line 117, in _call
return view_func(*args, **kwargs)
File
/usr/lib/python2.6/site-packages/Djblets-0.8.7-py2.6.egg/djblets/webapi/decorators.py,
line 117, in _call
return view_func(*args, **kwargs)
File
/usr/lib/python2.6/site-packages/Djblets-0.8.7-py2.6.egg/djblets/webapi/decorators.py,
line 287, in _validate
return view_func(*args, **new_kwargs)
File
/usr/lib/python2.6/site-packages/ReviewBoard-2.0.4-py2.6.egg/reviewboard/webapi/resources/base_review.py,
line 169, in create
**self.get_base_reply_to_field(*args, **kwargs))
File
/usr/lib/python2.6/site-packages/Djblets-0.8.7-py2.6.egg/djblets/db/managers.py,
line 53, in get_or_create
return self.get(**kwargs)
File
/usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/db/models/manager.py,
line 151, in get
return self.get_queryset().get(*args, **kwargs)
File
/usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/db/models/query.py,
line 310, in get
self.model._meta.object_name)
DoesNotExist: Review matching query does not exist.
WSGIRequest
path:/api/review-requests/3677/reviews/,
GET:QueryDict: {},
POST:QueryDict: {u'body_top': [u''], u'text_type': [u'plain'],
u'body_bottom': [u''], u'api_format': [u'json'], u'ship_it': [u'false']},
COOKIES:{'collapsediffs': 'True',
'csrftoken': 'v9zdlH2rkdux8ABIrOYXIoEZ3UOY3vB0',
'rbsessionid': '3vha1z6fnrabst0eneet4qjvgjji9b0i'},
META:{'CONTENT_LENGTH': '68',
'CONTENT_TYPE': 'application/x-www-form-urlencoded; charset=UTF-8',
'DOCUMENT_ROOT': '/var/www/reviewboard/htdocs',
'GATEWAY_INTERFACE': 'CGI/1.1',
'HTTP_ACCEPT': 'application/json, text/javascript, */*; q=0.01',
'HTTP_ACCEPT_ENCODING': 'gzip, deflate',
'HTTP_ACCEPT_LANGUAGE': 'en-US,en;q=0.5',
'HTTP_CACHE_CONTROL': 'no-cache',
'HTTP_CONNECTION': 'keep-alive',
'HTTP_COOKIE': 'csrftoken=v9zdlH2rkdux8ABIrOYXIoEZ3UOY3vB0;
rbsessionid=3vha1z6fnrabst0eneet4qjvgjji9b0i; collapsediffs=True',
'HTTP_HOST': 'reviewboard.cctechnol.com',
'HTTP_PRAGMA': 'no-cache',
'HTTP_REFERER': 'http://reviewboard.cctechnol.com/r/3677/diff/',
'HTTP_USER_AGENT': 'Mozilla/5.0 (X11; Linux x86_64; rv:30.0)
Gecko/20100101 Firefox/30.0',
'HTTP_X_REQUESTED_WITH': 'XMLHttpRequest',
'PATH_INFO': u'/api/review-requests/3677/reviews/',
'PATH_TRANSLATED':
'/var/www/reviewboard/htdocs/reviewboard.wsgi/api/review-requests/3677/reviews/',
'QUERY_STRING': '',
'REMOTE_ADDR': '10.0.1.85',
'REMOTE_PORT': '57902',
'REQUEST_METHOD': 'POST',
'REQUEST_URI': '/api/review-requests/3677/reviews/',
'SCRIPT_FILENAME': '/var/www/reviewboard/htdocs/reviewboard.wsgi',
'SCRIPT_NAME': u'',
'SERVER_ADDR': '10.0.0.68',
'SERVER_ADMIN': 'root@localhost',
'SERVER_NAME': 'reviewboard.cctechnol.com',
'SERVER_PORT': '80',
'SERVER_PROTOCOL': 'HTTP/1.1',
'SERVER_SIGNATURE': 'addressApache/2.2.15 (CentOS) Server at
reviewboard.cctechnol.com
Re: Migrating Reviewboard from 1.5 to 2.0.4
Hi Bogdan, Re-running the upgrade is guaranteed to fail, because the database is in an inconsistent state. The problem isn’t so much an upgrade from 1.5.x to 2.0.x.. Rather, it’s anything 2.0 to 2.0.4. Fortunately, I found the cause, and have put out a django-evolution 0.7.3 release. You should be able to upgrade that: sudo easy_install -U django_evolution And then restore your database dump and re-upgrade. It should work. (Please let me know either way.) We’ll be putting out a 2.0.5 shortly that requires this version. Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On July 25, 2014 at 2:06:23 AM, Bogdan Berezovyi (bod...@gmail.com) wrote: Hi Christian, Yes I have a backup, I'm playing with it on dev server, so can reimport at any time. I've also tried upgrading from 1.5.3 to 1.6.22 frist (as an intermidiary step) - this went smoothly Next upgrading from 1.6.22 to 2.0.4 gives me the same error first, but I'm able to rerun upgrade (no traceback) and then it gives the other error: 1. Error applying evolution: (1051, Unknown table 'auth_message') solution: Recreate table 2. CommandError: Error applying evolution: (1060, Duplicate column name 'permissions') solution: alter table accounts_localsiteprofile drop column permissions; 3. CommandError: Error applying evolution: (1060, Duplicate column name 'timezone') ... Should I follow the rabbit hole or just redump my database? Thanks, Bogdan On Thursday, July 24, 2014 10:43:49 PM UTC+3, Christian Hammond wrote: Hi, Do you have a backup of your 1.5.3 database? You’ll need one at this point, since the new database is in an inconsistent state. Christian -- Christian Hammond - chri...@beanbaginc.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On July 24, 2014 at 11:48:49 AM, Bogdan Berezovyi (bod...@gmail.com) wrote: Hi, I'm having trouble upgrading existing reviewboard 1.5.3 to the new release 2.0.4. After importing mysql dump and running rb-site upgrade I get the following error: CommandError: Error applying evolution: (1061, Duplicate key name 'scmtools_repository_97c59b73') I tried removing index as per one of earlier thread with similar error by running drop index scmtools_repository_97c59b73 on scmtools_repository; But this didn't help. If I rerun upgrade it crashes with traceback. Any help would be much appreciated. Bogdan -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Error 500 when posting comments
Hi Sara. Some questions for you.
When you say a reboot, was it of the full server, or just the web server? Did
this include the database server? (What type of database?)
When did the upgrade of Review Board to 2.0.4 happen, relative to the reboot?
I wouldn’t expect these errors unless you had some data corruption somewhere.
Was the reboot a clean reboot?
Are you getting that exact same error traceback for all review requests?
Are you able to see reviews on existing review requests?
Can you also make sure that people are actually logged in when posting this? I
want to rule out a session-related issue.
Christian
--
Christian Hammond - christ...@beanbaginc.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On July 25, 2014 at 10:29:17 AM, Sara Rayburn (sararayb...@gmail.com) wrote:
Hi all,
After a reboot of my reviewboard server, I am now getting Error 500 internal
server errors any time a user tries to submit a comment on a review request. I
have verified that I can add new review requests, and perform other edits on
those review requests. Here is a sample error:
Traceback (most recent call last):
File
/usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/core/handlers/base.py,
line 112, in get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File
/usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/views/decorators/cache.py,
line 52, in _wrapped_view_func
response = view_func(request, *args, **kwargs)
File
/usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/views/decorators/vary.py,
line 19, in inner_func
response = func(*args, **kwargs)
File
/usr/lib/python2.6/site-packages/Djblets-0.8.7-py2.6.egg/djblets/webapi/resources.py,
line 494, in __call__
request, method, view, api_format=api_format, *args, **kwargs)
File
/usr/lib/python2.6/site-packages/Djblets-0.8.7-py2.6.egg/djblets/webapi/resources.py,
line 565, in call_method_view
return view(request, *args, **kwargs)
File
/usr/lib/python2.6/site-packages/Djblets-0.8.7-py2.6.egg/djblets/webapi/resources.py,
line 747, in post
return self.create(*args, **kwargs)
File
/usr/lib/python2.6/site-packages/Djblets-0.8.7-py2.6.egg/djblets/webapi/decorators.py,
line 117, in _call
return view_func(*args, **kwargs)
File
/usr/lib/python2.6/site-packages/ReviewBoard-2.0.4-py2.6.egg/reviewboard/webapi/decorators.py,
line 110, in _check
return view_func(*args, **kwargs)
File
/usr/lib/python2.6/site-packages/Djblets-0.8.7-py2.6.egg/djblets/webapi/decorators.py,
line 117, in _call
return view_func(*args, **kwargs)
File
/usr/lib/python2.6/site-packages/Djblets-0.8.7-py2.6.egg/djblets/webapi/decorators.py,
line 138, in _checklogin
return view_func(*args, **kwargs)
File
/usr/lib/python2.6/site-packages/Djblets-0.8.7-py2.6.egg/djblets/webapi/decorators.py,
line 117, in _call
return view_func(*args, **kwargs)
File
/usr/lib/python2.6/site-packages/Djblets-0.8.7-py2.6.egg/djblets/webapi/decorators.py,
line 117, in _call
return view_func(*args, **kwargs)
File
/usr/lib/python2.6/site-packages/Djblets-0.8.7-py2.6.egg/djblets/webapi/decorators.py,
line 287, in _validate
return view_func(*args, **new_kwargs)
File
/usr/lib/python2.6/site-packages/ReviewBoard-2.0.4-py2.6.egg/reviewboard/webapi/resources/base_review.py,
line 169, in create
**self.get_base_reply_to_field(*args, **kwargs))
File
/usr/lib/python2.6/site-packages/Djblets-0.8.7-py2.6.egg/djblets/db/managers.py,
line 53, in get_or_create
return self.get(**kwargs)
File
/usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/db/models/manager.py,
line 151, in get
return self.get_queryset().get(*args, **kwargs)
File
/usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/db/models/query.py,
line 310, in get
self.model._meta.object_name)
DoesNotExist: Review matching query does not exist.
WSGIRequest
path:/api/review-requests/3677/reviews/,
GET:QueryDict: {},
POST:QueryDict: {u'body_top': [u''], u'text_type': [u'plain'], u'body_bottom':
[u''], u'api_format': [u'json'], u'ship_it': [u'false']},
COOKIES:{'collapsediffs': 'True',
'csrftoken': 'v9zdlH2rkdux8ABIrOYXIoEZ3UOY3vB0',
'rbsessionid': '3vha1z6fnrabst0eneet4qjvgjji9b0i'},
META:{'CONTENT_LENGTH': '68',
'CONTENT_TYPE': 'application/x-www-form-urlencoded; charset=UTF-8',
'DOCUMENT_ROOT': '/var/www/reviewboard/htdocs',
'GATEWAY_INTERFACE': 'CGI/1.1',
'HTTP_ACCEPT': 'application/json, text/javascript, */*; q=0.01',
'HTTP_ACCEPT_ENCODING': 'gzip, deflate',
'HTTP_ACCEPT_LANGUAGE': 'en-US,en;q=0.5',
'HTTP_CACHE_CONTROL': 'no-cache',
'HTTP_CONNECTION': 'keep-alive',
'HTTP_COOKIE': 'csrftoken=v9zdlH2rkdux8ABIrOYXIoEZ3UOY3vB0;
rbsessionid=3vha1z6fnrabst0eneet4qjvgjji9b0i; collapsediffs=True',
'HTTP_HOST': 'reviewboard.cctechnol.com',
'HTTP_PRAGMA': 'no-cache',
'HTTP_REFERER':
Re: Error 500 when posting comments
Hi Christian, See responses inline. I'm afraid this is a server corruption thing. If that's your opinion, is there some way to repair the db? On Friday, July 25, 2014 2:32:32 PM UTC-5, Christian Hammond wrote: Hi Sara. Some questions for you. When you say a reboot, was it of the full server, or just the web server? Did this include the database server? (What type of database?) Full server reboot, including the db. All requisite services are running, and there is read/write access to the db since we can create/view review requests. When did the upgrade of Review Board to 2.0.4 happen, relative to the reboot? Within a couple of days, however the server VM has been rebooted since the install. (Our VM host keeps dying) I wouldn’t expect these errors unless you had some data corruption somewhere. Was the reboot a clean reboot? This is not out of the question. The server is running in a VM on a dying server. I shutdown the VM to do an emergency back up, and when I relaunched it, all these problems occurred. Are you getting that exact same error traceback for all review requests? Yes, with the exception of the review request number Are you able to see reviews on existing review requests? Yes Can you also make sure that people are actually logged in when posting this? I want to rule out a session-related issue. I'm not sure how to verify this. I have logged out, logged back in, and tried to post. Our site is not public. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Can't upload diff for clearcase in 2.0.4
I installed Reviewboard 2.0.4 on Windows by using the Bitnami installer and
configured it for Clearcase dynamic view. I set the repository path to the
top of the view then ran rbt post --server=http:/localhost/reviewboard
--user=xxx --password=xxx -o --summary=test --debug from my view
directory. I could see rbt was able to generate the diff but it failed to
post it. Here below I pasted the error stacks from both the console and the
log file.
Any help or hint will be highly appreciated.
*Console Error*
Making HTTP GET request to
http://localhost/reviewboard/api/review-requests/
Making HTTP POST request to
http://localhost/reviewboard/api/review-requests/
Making HTTP GET request to
http://localhost/reviewboard/api/review-requests/1/diffs/
Making HTTP POST request to
http://localhost/reviewboard/api/review-requests/1/diffs/
Got HTTP error: 500: !DOCTYPE html
html
head
title500 - Internal Server Error | Review Board/title
/head
body
h1Something broke! (Error 500)/h1
p
It appears something broke when you tried to go to here. This is either
a bug in Review Board or a server configuration error. Please report
this to your administrator.
/p
/body
/title
Traceback (most recent call last):
File d:\reviewboard-2.0.4-0\python\Scripts\rbt-script.py, line 8, in
module
load_entry_point('rbtools==0.6.2', 'console_scripts', 'rbt')()
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\rbtools-0.6.2-py2.7.egg\rbtools\commands\main.py,
line 134, in main
command.run_from_argv([RB_MAIN, command_name] + args)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\rbtools-0.6.2-py2.7.egg\rbtools\commands\__init__.py,
line 416, in run_from_argv
exit_code = self.main(*args) or 0
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\rbtools-0.6.2-py2.7.egg\rbtools\commands\post.py,
line 784, in main
submit_as=self.options.submit_as)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\rbtools-0.6.2-py2.7.egg\rbtools\commands\post.py,
line 551, in post_request
raise CommandError(u'\n'.join(error_msg))
rbtools.commands.CommandError: Error uploading diff
HTTP 500
Your review request still exists, but the diff is not attached.
*Error stack from reviewboard.log*
2014-07-25 15:25:16,834 - ERROR - - Exception thrown for user liuz6163 at
http://localhost/reviewboard/api/review-requests/1/diffs/
[Error 267] The directory name is invalid
Traceback (most recent call last):
File D:\reviewboard-2.0.4-0\apps\django\django\core\handlers\base.py,
line 112, in get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File
D:\reviewboard-2.0.4-0\apps\django\django\views\decorators\cache.py, line
52, in _wrapped_view_func
response = view_func(request, *args, **kwargs)
File
D:\reviewboard-2.0.4-0\apps\django\django\views\decorators\vary.py, line
19, in inner_func
response = func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\resources.py,
line 494, in __call__
request, method, view, api_format=api_format, *args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\resources.py,
line 565, in call_method_view
return view(request, *args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\resources.py,
line 747, in post
return self.create(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\decorators.py,
line 117, in _call
return view_func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\decorators.py,
line 138, in _checklogin
return view_func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\decorators.py,
line 117, in _call
return view_func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\apps\reviewboard\Lib\site-packages\ReviewBoard-2.0.4-py2.7.egg\reviewboard\webapi\decorators.py,
line 110, in _check
return view_func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\decorators.py,
line 117, in _call
return view_func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\decorators.py,
line 117, in _call
return view_func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\decorators.py,
line 287, in _validate
return view_func(*args, **new_kwargs)
File
D:\reviewboard-2.0.4-0\apps\reviewboard\Lib\site-packages\ReviewBoard-2.0.4-py2.7.egg\reviewboard\webapi\resources\diff.py,
line 283, in create
request=request)
File
Reviewboard 2.0.4 failed to post diff for ClearCase
I installed ReviewBoard 2.0.4 on Windows using the Bitnami installer. Then
I set it to clearcase and the repository is the top of the view. When I run
rbt post --server=http://localhost/reviewboard --debug --user=xxx
--password=xxx from the view directory, a 500 error occurred (I attached
both the console error and the log file error below). Any help will be
highly appreciated.
*Error from console*
Making HTTP GET request to
http://localhost/reviewboard/api/review-requests/
Making HTTP POST request to
http://localhost/reviewboard/api/review-requests/
Making HTTP GET request to
http://localhost/reviewboard/api/review-requests/1/diffs/
Making HTTP POST request to
http://localhost/reviewboard/api/review-requests/1/diffs/
Got HTTP error: 500: !DOCTYPE html
html
head
title500 - Internal Server Error | Review Board/title
/head
body
h1Something broke! (Error 500)/h1
p
It appears something broke when you tried to go to here. This is either
a bug in Review Board or a server configuration error. Please report
this to your administrator.
/p
/body
/title
Traceback (most recent call last):
File d:\reviewboard-2.0.4-0\python\Scripts\rbt-script.py, line 8, in
module
load_entry_point('rbtools==0.6.2', 'console_scripts', 'rbt')()
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\rbtools-0.6.2-py2.7.egg\rbtools\commands\main.py,
line 134, in main
command.run_from_argv([RB_MAIN, command_name] + args)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\rbtools-0.6.2-py2.7.egg\rbtools\commands\__init__.py,
line 416, in run_from_argv
exit_code = self.main(*args) or 0
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\rbtools-0.6.2-py2.7.egg\rbtools\commands\post.py,
line 784, in main
submit_as=self.options.submit_as)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\rbtools-0.6.2-py2.7.egg\rbtools\commands\post.py,
line 551, in post_request
raise CommandError(u'\n'.join(error_msg))
rbtools.commands.CommandError: Error uploading diff
HTTP 500
Your review request still exists, but the diff is not attached.
http://localhost/reviewboard/r/1/
*Error from reviewboard.log file*
2014-07-25 15:25:16,834 - ERROR - - Exception thrown for user liuzy163 at
http://localhost/reviewboard/api/review-requests/1/diffs/
[Error 267] The directory name is invalid
Traceback (most recent call last):
File D:\reviewboard-2.0.4-0\apps\django\django\core\handlers\base.py,
line 112, in get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File
D:\reviewboard-2.0.4-0\apps\django\django\views\decorators\cache.py, line
52, in _wrapped_view_func
response = view_func(request, *args, **kwargs)
File
D:\reviewboard-2.0.4-0\apps\django\django\views\decorators\vary.py, line
19, in inner_func
response = func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\resources.py,
line 494, in __call__
request, method, view, api_format=api_format, *args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\resources.py,
line 565, in call_method_view
return view(request, *args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\resources.py,
line 747, in post
return self.create(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\decorators.py,
line 117, in _call
return view_func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\decorators.py,
line 138, in _checklogin
return view_func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\decorators.py,
line 117, in _call
return view_func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\apps\reviewboard\Lib\site-packages\ReviewBoard-2.0.4-py2.7.egg\reviewboard\webapi\decorators.py,
line 110, in _check
return view_func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\decorators.py,
line 117, in _call
return view_func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\decorators.py,
line 117, in _call
return view_func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\decorators.py,
line 287, in _validate
return view_func(*args, **new_kwargs)
File
D:\reviewboard-2.0.4-0\apps\reviewboard\Lib\site-packages\ReviewBoard-2.0.4-py2.7.egg\reviewboard\webapi\resources\diff.py,
line 283, in create
request=request)
File
D:\reviewboard-2.0.4-0\apps\reviewboard\Lib\site-packages\ReviewBoard-2.0.4-py2.7.egg\reviewboard\reviews\forms.py,
line 95, in __init__
data, *args, **kwargs)
File
Automate Review Board
Hi, I have following setup of reviewboard and Subversion : Apache Subversion hosted under SLES 10 SP1 . ReviewBoard installed on Window using BitNami stack. I already have a post-commit script to send email notifications for each commit under SLES, Now i want to automate the process in such a way that after each commit there should be a review request added (Review board in installed in some other machine) automatically. I tried to search and found post-review command to be used for that , I would like to know this post-review command is a part of reviewboard itself ? If yes then my reviewboard installation is on another machine then how SLES will execute a script containing post-review command. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Automate Review Board
On 2014-07-25 08:54, Randhir Singh wrote: I have following setup of reviewboard and Subversion : Apache Subversion hosted under SLES 10 SP1 . ReviewBoard installed on Window using BitNami stack. I already have a post-commit script to send email notifications for each commit under SLES, Now i want to automate the process in such a way that after each commit there should be a review request added (Review board in installed in some other machine) automatically. I tried to search and found post-review command to be used for that , I would like to know this post-review command is a part of reviewboard itself ? If yes then my reviewboard installation is on another machine then how SLES will execute a script containing post-review command. post-review is a script that is part of the RBTools package. That's part of review board in that it's made and distributed by the same folks, but it's a separate package, and also one normally installed on (all) developer's machines. Certainly you can install and run it on a machine other than your RB server! Note also, however, that post-review is deprecated. The new thing is the rbt tool. To oversimplify, rbt post replaces post-review. See also https://www.reviewboard.org/docs/rbtools/0.6/. -- Matthew -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Git configuration woes
I've been evaluating the powerpack. Is there a way to have the GitHub Enterprise repository hosting to use token based authentication rather than a user and password? We enforce password aging (sadly) and I don't fancy having to fix the same duplicated account on every repo every 90 days. For that matter it would be nice to be able to share the authentication information and not have it duplicated at all. Guy On Saturday, July 12, 2014 5:16:37 PM UTC-7, Christian Hammond wrote: The issue is the way they handle authentication and access control. It used to be that a raw URL worked fine, but due to changes made in their API, it’s no longer useable. For the data we need, in a way that works reliably, we have to use their API. Christian -- Christian Hammond - chri...@beanbaginc.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On July 12, 2014 at 5:11:23 PM, Guy Gascoigne-Piggford ( guy.pi...@gmail.com javascript:) wrote: is the issue the https part of the raw url mask? On Saturday, July 12, 2014 4:55:20 PM UTC-7, Christian Hammond wrote: Git has no ability to fetch files remotely via the protocol, which is why the raw URL mask is used. However, this is only useful for certain services, and GitHub Enterprise is not one of them. We provide official support for GitHub Enterprise as part of Power Pack, which also offers PDF document review and, soon, reporting functionality. This is at https://www.reviewboard.org/powerpack/. You would need to set up a trial license or purchase a full license for your server. Then, using GitHub Enterprise is as simple as adding a new repository, choosing GitHub Enterprise as the hosting service, and providing the details on which repository you want to add. Christian -- Christian Hammond - chri...@beanbaginc.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On July 12, 2014 at 4:52:54 PM, Guy Gascoigne-Piggford ( guy.pi...@gmail.com) wrote: We're beginning the switch over to a locally hosted Github Enterprise from bzr and I'm looking at configuring reviewboard to work with git. I've tried all sorts of permutations of the git repository settings but never get past a rather bland permission denied error. Is there any way to get more details about what's broken? Using reviewboard 1.7.25 I've enabled debug logging in admin UI, but all I ever see are lines like: 2014-07-12 23:30:38,023 - DEBUG - - GitTool: Attempting ssh connection with host: github.hostname.com, username: git with no further details, no idea as to whether this worked or failed. My repository configuration is: repository type: Git path: g...@github.hidden.com:ggp/testProject.git mirrorPath: blank raw file mask: https://github.hidden.com/ggp/testProject/raw/ revision/filename username: blank password: blank I've tried innumerable permutations of this, most of them seeming to have zero effect. I have an ssh key installed, it appears to be correctly readable. It does match one that's installed in our github. The web server is running as user apache (on a Centos box), as apache I've been able to run: ssh -vT g...@github.hidden.com which is successful. and: DEBUG_RBSSH=1 rbssh g...@github.hidden.com Which I think is successful. It outputs an exception because the Channel is closed, but the rbssh*.log file says that authentication was successful. 07-12 16:44 paramiko.transport DEBUGuserauth is OK 07-12 16:44 paramiko.transport INFO Authentication (publickey) successful! 07-12 16:44 paramiko.transport DEBUG[chan 1] Max packet in: 34816 bytes 07-12 16:44 paramiko.transport DEBUGDebug msg: Forced command. 07-12 16:44 paramiko.transport DEBUGDebug msg: Port forwarding disabled. 07-12 16:44 paramiko.transport DEBUGDebug msg: X11 forwarding disabled. 07-12 16:44 paramiko.transport DEBUGDebug msg: Agent forwarding disabled. 07-12 16:44 paramiko.transport DEBUGDebug msg: Pty allocation disabled. 07-12 16:44 paramiko.transport DEBUG[chan 1] Max packet out: 32768 bytes 07-12 16:44 paramiko.transport INFO Secsh channel 1 opened. 07-12 16:44 root DEBUG!!! Using PosixHandler 07-12 16:44 root DEBUG!!! Opening shell 07-12 16:44 paramiko.transport DEBUG[chan 1] EOF sent (1) /var/log/httpd/error_log isn't any more informative. I'm missing something, can someone point me in the right direction please? Thanks - Guy -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from
Re: Git configuration woes
Hi, The login and password is just used the first time to fetch a token. We never store those credentials. Instead, we pass them directly to the GitHub Enterprise API and store the resulting token. That token will last until you revoke it on GitHub Enterprise. We’re working on a full redesign of the repository page for a future release, which will make this more clear and cause a token to be fetched client-side, causing the username/password to never even go through our APIs. Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On July 25, 2014 at 2:26:07 PM, Guy Gascoigne-Piggford (guy.piggf...@gmail.com) wrote: I've been evaluating the powerpack. Is there a way to have the GitHub Enterprise repository hosting to use token based authentication rather than a user and password? We enforce password aging (sadly) and I don't fancy having to fix the same duplicated account on every repo every 90 days. For that matter it would be nice to be able to share the authentication information and not have it duplicated at all. Guy On Saturday, July 12, 2014 5:16:37 PM UTC-7, Christian Hammond wrote: The issue is the way they handle authentication and access control. It used to be that a raw URL worked fine, but due to changes made in their API, it’s no longer useable. For the data we need, in a way that works reliably, we have to use their API. Christian -- Christian Hammond - chri...@beanbaginc.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On July 12, 2014 at 5:11:23 PM, Guy Gascoigne-Piggford (guy.pi...@gmail.com) wrote: is the issue the https part of the raw url mask? On Saturday, July 12, 2014 4:55:20 PM UTC-7, Christian Hammond wrote: Git has no ability to fetch files remotely via the protocol, which is why the raw URL mask is used. However, this is only useful for certain services, and GitHub Enterprise is not one of them. We provide official support for GitHub Enterprise as part of Power Pack, which also offers PDF document review and, soon, reporting functionality. This is at https://www.reviewboard.org/powerpack/. You would need to set up a trial license or purchase a full license for your server. Then, using GitHub Enterprise is as simple as adding a new repository, choosing GitHub Enterprise as the hosting service, and providing the details on which repository you want to add. Christian -- Christian Hammond - chri...@beanbaginc.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On July 12, 2014 at 4:52:54 PM, Guy Gascoigne-Piggford (guy.pi...@gmail.com) wrote: We're beginning the switch over to a locally hosted Github Enterprise from bzr and I'm looking at configuring reviewboard to work with git. I've tried all sorts of permutations of the git repository settings but never get past a rather bland permission denied error. Is there any way to get more details about what's broken? Using reviewboard 1.7.25 I've enabled debug logging in admin UI, but all I ever see are lines like: 2014-07-12 23:30:38,023 - DEBUG - - GitTool: Attempting ssh connection with host: github.hostname.com, username: git with no further details, no idea as to whether this worked or failed. My repository configuration is: repository type: Git path: g...@github.hidden.com:ggp/testProject.git mirrorPath: blank raw file mask: https://github.hidden.com/ggp/testProject/raw/revision/filename username: blank password: blank I've tried innumerable permutations of this, most of them seeming to have zero effect. I have an ssh key installed, it appears to be correctly readable. It does match one that's installed in our github. The web server is running as user apache (on a Centos box), as apache I've been able to run: ssh -vT g...@github.hidden.com which is successful. and: DEBUG_RBSSH=1 rbssh g...@github.hidden.com Which I think is successful. It outputs an exception because the Channel is closed, but the rbssh*.log file says that authentication was successful. 07-12 16:44 paramiko.transport DEBUG userauth is OK 07-12 16:44 paramiko.transport INFO Authentication (publickey) successful! 07-12 16:44 paramiko.transport DEBUG [chan 1] Max packet in: 34816 bytes 07-12 16:44 paramiko.transport DEBUG Debug msg: Forced command. 07-12 16:44 paramiko.transport DEBUG Debug msg: Port forwarding disabled. 07-12 16:44 paramiko.transport DEBUG Debug msg: X11 forwarding disabled. 07-12 16:44 paramiko.transport DEBUG Debug msg: Agent forwarding disabled. 07-12 16:44 paramiko.transport DEBUG Debug msg: Pty allocation disabled. 07-12 16:44 paramiko.transport DEBUG [chan 1] Max packet out: 32768 bytes 07-12 16:44 paramiko.transport INFO Secsh channel 1 opened. 07-12 16:44 root DEBUG !!! Using PosixHandler 07-12 16:44 root DEBUG !!! Opening shell 07-12 16:44
Re: Can't upload diff for clearcase in 2.0.4
Hi,
You’re going to need to go through Bitnami support for this. This looks
specific to their install.
Christian
--
Christian Hammond - christ...@beanbaginc.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On July 25, 2014 at 1:15:18 PM, liuzy163 (zhiyongliu2...@gmail.com) wrote:
I installed Reviewboard 2.0.4 on Windows by using the Bitnami installer and
configured it for Clearcase dynamic view. I set the repository path to the top
of the view then ran rbt post --server=http:/localhost/reviewboard --user=xxx
--password=xxx -o --summary=test --debug from my view directory. I could see
rbt was able to generate the diff but it failed to post it. Here below I pasted
the error stacks from both the console and the log file.
Any help or hint will be highly appreciated.
Console Error
Making HTTP GET request to http://localhost/reviewboard/api/review-requests/
Making HTTP POST request to
http://localhost/reviewboard/api/review-requests/
Making HTTP GET request to
http://localhost/reviewboard/api/review-requests/1/diffs/
Making HTTP POST request to
http://localhost/reviewboard/api/review-requests/1/diffs/
Got HTTP error: 500: !DOCTYPE html
html
head
title500 - Internal Server Error | Review Board/title
/head
body
h1Something broke! (Error 500)/h1
p
It appears something broke when you tried to go to here. This is either
a bug in Review Board or a server configuration error. Please report
this to your administrator.
/p
/body
/title
Traceback (most recent call last):
File d:\reviewboard-2.0.4-0\python\Scripts\rbt-script.py, line 8, in
module
load_entry_point('rbtools==0.6.2', 'console_scripts', 'rbt')()
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\rbtools-0.6.2-py2.7.egg\rbtools\commands\main.py,
line 134, in main
command.run_from_argv([RB_MAIN, command_name] + args)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\rbtools-0.6.2-py2.7.egg\rbtools\commands\__init__.py,
line 416, in run_from_argv
exit_code = self.main(*args) or 0
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\rbtools-0.6.2-py2.7.egg\rbtools\commands\post.py,
line 784, in main
submit_as=self.options.submit_as)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\rbtools-0.6.2-py2.7.egg\rbtools\commands\post.py,
line 551, in post_request
raise CommandError(u'\n'.join(error_msg))
rbtools.commands.CommandError: Error uploading diff
HTTP 500
Your review request still exists, but the diff is not attached.
Error stack from reviewboard.log
2014-07-25 15:25:16,834 - ERROR - - Exception thrown for user liuz6163 at
http://localhost/reviewboard/api/review-requests/1/diffs/
[Error 267] The directory name is invalid
Traceback (most recent call last):
File D:\reviewboard-2.0.4-0\apps\django\django\core\handlers\base.py, line
112, in get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File D:\reviewboard-2.0.4-0\apps\django\django\views\decorators\cache.py,
line 52, in _wrapped_view_func
response = view_func(request, *args, **kwargs)
File D:\reviewboard-2.0.4-0\apps\django\django\views\decorators\vary.py,
line 19, in inner_func
response = func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\resources.py,
line 494, in __call__
request, method, view, api_format=api_format, *args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\resources.py,
line 565, in call_method_view
return view(request, *args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\resources.py,
line 747, in post
return self.create(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\decorators.py,
line 117, in _call
return view_func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\decorators.py,
line 138, in _checklogin
return view_func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\decorators.py,
line 117, in _call
return view_func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\apps\reviewboard\Lib\site-packages\ReviewBoard-2.0.4-py2.7.egg\reviewboard\webapi\decorators.py,
line 110, in _check
return view_func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\decorators.py,
line 117, in _call
return view_func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\decorators.py,
line 117, in _call
return view_func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\decorators.py,
line 287, in _validate
return
Re: Error 500 when posting comments
On July 25, 2014 at 12:38:06 PM, Sara Rayburn (sararayb...@gmail.com) wrote: Hi Christian, See responses inline. I'm afraid this is a server corruption thing. If that's your opinion, is there some way to repair the db? Possibly, depending on what’s wrong. I don’t know enough about the state of your database to say. A few more questions for now: 1) Before upgrading to 2.0.4, what version were you running? 2) Did you have these problems immediately after upgrading, or just after the reboot? 3) Are these review requests on private repositories/groups? 4) Does this only break when replying to reviews? Can new reviews be posted? Christian On Friday, July 25, 2014 2:32:32 PM UTC-5, Christian Hammond wrote: Hi Sara. Some questions for you. When you say a reboot, was it of the full server, or just the web server? Did this include the database server? (What type of database?) Full server reboot, including the db. All requisite services are running, and there is read/write access to the db since we can create/view review requests. When did the upgrade of Review Board to 2.0.4 happen, relative to the reboot? Within a couple of days, however the server VM has been rebooted since the install. (Our VM host keeps dying) I wouldn’t expect these errors unless you had some data corruption somewhere. Was the reboot a clean reboot? This is not out of the question. The server is running in a VM on a dying server. I shutdown the VM to do an emergency back up, and when I relaunched it, all these problems occurred. Are you getting that exact same error traceback for all review requests? Yes, with the exception of the review request number Are you able to see reviews on existing review requests? Yes Can you also make sure that people are actually logged in when posting this? I want to rule out a session-related issue. I'm not sure how to verify this. I have logged out, logged back in, and tried to post. Our site is not public. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Formatting errors in description field
OK, I believe that the problem is the indentation. Markdown treats indented text as a code block, and won't handle any markdown syntax in it. -David On Thu, Jul 24, 2014 at 11:15 PM, Philip Schiffer philip.schif...@sprylab.com wrote: Sorry for the late answer - I did not get any notification :/ Am Donnerstag, 17. Juli 2014 22:30:38 UTC+2 schrieb David Trowbridge: Can you show what the source markdown looks like? (Click the pencil and then copy/paste/redact) -David On Thu, Jul 17, 2014 at 2:34 AM, Philip Schiffer philip@sprylab.com wrote: Hello everyone, I have upgraded our reviewboard installation from 1.7.x to 2.0.3. Unfortunately we have some issues with the formatting of the description field. We are using the post-review tool in our scripts to post our reviews. Inside the description field we put the git commit log entries. As you can see in the attachment, there are problems displaying the links. I've searched the bug tracker but unfortunately I'm getting http 500 errors from google code for this issue: https://code.google.com/p/ reviewboard/issues/detail?id=3377 -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Git configuration woes
Nice, that makes much more sense. Guy On Jul 25, 2014, at 2:28 PM, Christian Hammond christ...@beanbaginc.com wrote: Hi, The login and password is just used the first time to fetch a token. We never store those credentials. Instead, we pass them directly to the GitHub Enterprise API and store the resulting token. That token will last until you revoke it on GitHub Enterprise. We're working on a full redesign of the repository page for a future release, which will make this more clear and cause a token to be fetched client-side, causing the username/password to never even go through our APIs. Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On July 25, 2014 at 2:26:07 PM, Guy Gascoigne-Piggford (guy.piggf...@gmail.com) wrote: I've been evaluating the powerpack. Is there a way to have the GitHub Enterprise repository hosting to use token based authentication rather than a user and password? We enforce password aging (sadly) and I don't fancy having to fix the same duplicated account on every repo every 90 days. For that matter it would be nice to be able to share the authentication information and not have it duplicated at all. Guy On Saturday, July 12, 2014 5:16:37 PM UTC-7, Christian Hammond wrote: The issue is the way they handle authentication and access control. It used to be that a raw URL worked fine, but due to changes made in their API, it's no longer useable. For the data we need, in a way that works reliably, we have to use their API. Christian -- Christian Hammond - chri...@beanbaginc.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On July 12, 2014 at 5:11:23 PM, Guy Gascoigne-Piggford (guy.pi...@gmail.com) wrote: is the issue the https part of the raw url mask? On Saturday, July 12, 2014 4:55:20 PM UTC-7, Christian Hammond wrote: Git has no ability to fetch files remotely via the protocol, which is why the raw URL mask is used. However, this is only useful for certain services, and GitHub Enterprise is not one of them. We provide official support for GitHub Enterprise as part of Power Pack, which also offers PDF document review and, soon, reporting functionality. This is at https://www.reviewboard.org/powerpack/. You would need to set up a trial license or purchase a full license for your server. Then, using GitHub Enterprise is as simple as adding a new repository, choosing GitHub Enterprise as the hosting service, and providing the details on which repository you want to add. Christian -- Christian Hammond - chri...@beanbaginc.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On July 12, 2014 at 4:52:54 PM, Guy Gascoigne-Piggford (guy.pi...@gmail.com) wrote: We're beginning the switch over to a locally hosted Github Enterprise from bzr and I'm looking at configuring reviewboard to work with git. I've tried all sorts of permutations of the git repository settings but never get past a rather bland permission denied error. Is there any way to get more details about what's broken? Using reviewboard 1.7.25 I've enabled debug logging in admin UI, but all I ever see are lines like: 2014-07-12 23:30:38,023 - DEBUG - - GitTool: Attempting ssh connection with host: github.hostname.com, username: git with no further details, no idea as to whether this worked or failed. My repository configuration is: repository type: Git path: g...@github.hidden.com:ggp/testProject.git mirrorPath: blank raw file mask: https://github.hidden.com/ggp/testProject/raw/revision/filename username: blank password: blank I've tried innumerable permutations of this, most of them seeming to have zero effect. I have an ssh key installed, it appears to be correctly readable. It does match one that's installed in our github. The web server is running as user apache (on a Centos box), as apache I've been able to run: ssh -vT g...@github.hidden.com which is successful. and: DEBUG_RBSSH=1 rbssh g...@github.hidden.com Which I think is successful. It outputs an exception because the Channel is closed, but the rbssh*.log file says that authentication was successful. 07-12 16:44 paramiko.transport DEBUGuserauth is OK 07-12 16:44 paramiko.transport INFO Authentication (publickey) successful! 07-12 16:44 paramiko.transport DEBUG[chan 1] Max packet in: 34816 bytes 07-12 16:44 paramiko.transport DEBUGDebug msg: Forced command. 07-12 16:44 paramiko.transport DEBUGDebug msg: Port forwarding disabled. 07-12 16:44 paramiko.transport DEBUGDebug msg: X11 forwarding disabled. 07-12 16:44 paramiko.transport DEBUGDebug msg: Agent forwarding disabled. 07-12 16:44 paramiko.transport DEBUGDebug msg: Pty allocation disabled. 07-12 16:44
Re: Error when diff files on ReviewBoard site
This is still not the contents of the log file. -David On Tue, Jul 22, 2014 at 11:52 PM, hoàng tuấn hoangnt00...@gmail.com wrote: Dear Mr David, I get this log when i click at *ViewDiff* or *click at the file* on *ReviewRequest* I sent to you all i got. ===*Review Request* https://lh4.googleusercontent.com/-tdnYHF7hsHY/U89aaHzso-I/AC0/lw9bYueKplU/s1600/1.PNG https://lh4.googleusercontent.com/-18eOTGuXgJ8/U89afS3T37I/AC8/ncjIHYTcVXc/s1600/2.PNG ==*Checking in /tmp* = https://lh5.googleusercontent.com/-4DDbrqK3d0o/U89akHOVSUI/ADE/QxrO4ALGWFY/s1600/3.PNG https://lh6.googleusercontent.com/-kLgNeLEyEug/U89azuNI4HI/ADM/S1VcOz-QFLE/s1600/4.PNG https://lh4.googleusercontent.com/-cqnElVbRsuY/U89a45npPDI/ADU/Q0K67W76Ebo/s1600/5.PNG *Config Repository* = https://lh6.googleusercontent.com/-pW90iAVQScc/U89a97vXYpI/ADc/2S5sy9HJ-AU/s1600/6.PNG If i miss anything, please let me know and i will send to you. Thank you for your support and your enthusiasm!!! Best Regards, Nguyen Tuan Hoang -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: New Review Board 1.7.27 and 2.0.4 security releases
I don't actually see version 2.0.4 at http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ Index of /releases/ReviewBoard/2.0/ -- ReviewBoard-2.0-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0-py2.6.eggReviewBoard-2.0-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0-py2.7.eggReviewBoard-2.0.1-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.1-py2.6.eggReviewBoard-2.0.1-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.1-py2.7.eggReviewBoard-2.0.1.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.1.sha256sumReviewBoard-2.0.1.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.1.tar.gzReviewBoard-2.0.2-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.2-py2.6.eggReviewBoard-2.0.2-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.2-py2.7.eggReviewBoard-2.0.2.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.2.sha256sumReviewBoard-2.0.2.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.2.tar.gzReviewBoard-2.0.3-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.3-py2.6.eggReviewBoard-2.0.3-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.3-py2.7.eggReviewBoard-2.0.3.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.3.sha256sumReviewBoard-2.0.3.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.3.tar.gzReviewBoard-2.0.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.sha256sumReviewBoard-2.0.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.tar.gzReviewBoard-2.0beta1-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta1-py2.6.eggReviewBoard-2.0beta1-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta1-py2.7.eggReviewBoard-2.0beta1.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta1.sha256sumReviewBoard-2.0beta1.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta1.tar.gzReviewBoard-2.0beta2-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta2-py2.6.eggReviewBoard-2.0beta2-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta2-py2.7.eggReviewBoard-2.0beta2.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta2.sha256sumReviewBoard-2.0beta2.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta2.tar.gzReviewBoard-2.0beta3-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta3-py2.6.eggReviewBoard-2.0beta3-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta3-py2.7.eggReviewBoard-2.0beta3.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta3.sha256sumReviewBoard-2.0beta3.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta3.tar.gzReviewBoard-2.0rc1-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc1-py2.6.eggReviewBoard-2.0rc1-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc1-py2.7.eggReviewBoard-2.0rc1.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc1.sha256sumReviewBoard-2.0rc1.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc1.tar.gzReviewBoard-2.0rc2-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc2-py2.6.eggReviewBoard-2.0rc2-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc2-py2.7.eggReviewBoard-2.0rc2.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc2.sha256sumReviewBoard-2.0rc2.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc2.tar.gzReviewBoard-2.0rc3-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc3-py2.6.eggReviewBoard-2.0rc3-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc3-py2.7.eggReviewBoard-2.0rc3.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc3.sha256sumReviewBoard-2.0rc3.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc3.tar.gz On Tuesday, July 22, 2014 5:23:35 AM UTC-4, Christian Hammond wrote: Hi everyone, We just put out a couple of new Review Board releases: 1.7.27 and 2.0.4. Both fix a couple of security vulnerabilities
Re: New Review Board 1.7.27 and 2.0.4 security releases
We temporarily took it down in order to address an issue with upgrades from earlier releases that users were hitting. We'll have a 2.0.5 out tonight that addresses these issues. Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Fri, Jul 25, 2014 at 3:51 PM, Erik Lattimore erik.l...@gmail.com wrote: I don't actually see version 2.0.4 at http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ Index of /releases/ReviewBoard/2.0/ -- ReviewBoard-2.0-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0-py2.6.eggReviewBoard-2.0-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0-py2.7.eggReviewBoard-2.0.1-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.1-py2.6.eggReviewBoard-2.0.1-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.1-py2.7.eggReviewBoard-2.0.1.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.1.sha256sumReviewBoard-2.0.1.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.1.tar.gzReviewBoard-2.0.2-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.2-py2.6.eggReviewBoard-2.0.2-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.2-py2.7.eggReviewBoard-2.0.2.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.2.sha256sumReviewBoard-2.0.2.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.2.tar.gzReviewBoard-2.0.3-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.3-py2.6.eggReviewBoard-2.0.3-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.3-py2.7.eggReviewBoard-2.0.3.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.3.sha256sumReviewBoard-2.0.3.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.3.tar.gzReviewBoard-2.0.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.sha256sumReviewBoard-2.0.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.tar.gzReviewBoard-2.0beta1-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta1-py2.6.eggReviewBoard-2.0beta1-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta1-py2.7.eggReviewBoard-2.0beta1.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta1.sha256sumReviewBoard-2.0beta1.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta1.tar.gzReviewBoard-2.0beta2-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta2-py2.6.eggReviewBoard-2.0beta2-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta2-py2.7.eggReviewBoard-2.0beta2.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta2.sha256sumReviewBoard-2.0beta2.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta2.tar.gzReviewBoard-2.0beta3-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta3-py2.6.eggReviewBoard-2.0beta3-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta3-py2.7.eggReviewBoard-2.0beta3.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta3.sha256sumReviewBoard-2.0beta3.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta3.tar.gzReviewBoard-2.0rc1-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc1-py2.6.eggReviewBoard-2.0rc1-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc1-py2.7.eggReviewBoard-2.0rc1.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc1.sha256sumReviewBoard-2.0rc1.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc1.tar.gzReviewBoard-2.0rc2-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc2-py2.6.eggReviewBoard-2.0rc2-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc2-py2.7.eggReviewBoard-2.0rc2.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc2.sha256sumReviewBoard-2.0rc2.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc2.tar.gzReviewBoard-2.0rc3-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc3-py2.6.eggReviewBoard-2.0rc3-py2.7.egg
Re: Error 500 when posting comments
Hi Sara, Okay. So there are a couple options here for figuring this out. One will require a support contract (either a one-time support session for an hourly fee, or a one-year contract that would include such sessions). Through that, we could share more information over a private tracker, and we could set up either a live chat or phone call, along with screen sharing. This would be the quickest way to get things figured out. Otherwise, we can continue on with e-mail here. I can send you some commands that would help provide more information, so I could at least see what’s going wrong. There will be some back-and-forth going, but I’ll be around for the next several hours now. Let me know what sounds best for you! Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On July 25, 2014 at 3:01:27 PM, Sara Rayburn (sararayb...@gmail.com) wrote: Responses inline. On Jul 25, 2014 4:43 PM, Christian Hammond christ...@beanbaginc.com wrote: On July 25, 2014 at 12:38:06 PM, Sara Rayburn (sararayb...@gmail.com) wrote: Hi Christian, See responses inline. I'm afraid this is a server corruption thing. If that's your opinion, is there some way to repair the db? Possibly, depending on what’s wrong. I don’t know enough about the state of your database to say. A few more questions for now: 1) Before upgrading to 2.0.4, what version were you running? 2.0.3 2) Did you have these problems immediately after upgrading, or just after the reboot? This specific problem is new since the reboot, but we were having occasional issues even at .3 . I posted another question last week with another error message that no one responded to. 3) Are these review requests on private repositories/groups? They do belong to groups. 4) Does this only break when replying to reviews? Can new reviews be posted? Yes. All other functionality seems to work. Sara Christian On Friday, July 25, 2014 2:32:32 PM UTC-5, Christian Hammond wrote: Hi Sara. Some questions for you. When you say a reboot, was it of the full server, or just the web server? Did this include the database server? (What type of database?) Full server reboot, including the db. All requisite services are running, and there is read/write access to the db since we can create/view review requests. When did the upgrade of Review Board to 2.0.4 happen, relative to the reboot? Within a couple of days, however the server VM has been rebooted since the install. (Our VM host keeps dying) I wouldn’t expect these errors unless you had some data corruption somewhere. Was the reboot a clean reboot? This is not out of the question. The server is running in a VM on a dying server. I shutdown the VM to do an emergency back up, and when I relaunched it, all these problems occurred. Are you getting that exact same error traceback for all review requests? Yes, with the exception of the review request number Are you able to see reviews on existing review requests? Yes Can you also make sure that people are actually logged in when posting this? I want to rule out a session-related issue. I'm not sure how to verify this. I have logged out, logged back in, and tried to post. Our site is not public. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 3500 in reviewboard: Update from RB 1.6.2 to 2.0.3 failed.
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 3500 by ad643...@gmail.com: Update from RB 1.6.2 to 2.0.3 failed.
http://code.google.com/p/reviewboard/issues/detail?id=3500
What version are you running?
1.6.2
What's the URL of the page containing the problem?
What steps will reproduce the problem?
1. use easy_install -U ReviewBoard to update to 2.0.3
2. rb-site upgrade /path/to/site
3.
What is the expected output? What do you see instead?
I expect the update to succeed. It doesn't. The backtrace:
Traceback (most recent call last):
File /usr/bin/rb-site, line 9, in module
load_entry_point('ReviewBoard==2.0.3', 'console_scripts', 'rb-site')()
File /usr/lib/python2.6/site-packages/ReviewBoard-2.0.3-py2.6.egg/reviewboard/cmdline/rbsite.py,
line 1859, in main
command.run()
File /usr/lib/python2.6/site-packages/ReviewBoard-2.0.3-py2.6.egg/reviewboard/cmdline/rbsite.py,
line 1657, in run
diff_dedup_needed = site.get_diff_dedup_needed()
File /usr/lib/python2.6/site-packages/ReviewBoard-2.0.3-py2.6.egg/reviewboard/cmdline/rbsite.py,
line 449, in get_diff_dedup_needed
return FileDiff.objects.unmigrated().count() 0
File /usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/db/models/query.py,
line 294, in count
return self.query.get_count(using=self.db)
File /usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/db/models/sql/query.py,
line 390, in get_count
number = obj.get_aggregation(using=using)[None]
File /usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/db/models/sql/query.py,
line 356, in get_aggregation
result = query.get_compiler(using).execute_sql(SINGLE)
File /usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/db/models/sql/compiler.py,
line 786, in execute_sql
cursor.execute(sql, params)
File /usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/db/backends/util.py,
line 53, in execute
return self.cursor.execute(sql, params)
File /usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/db/utils.py,
line 99, in __exit__
six.reraise(dj_exc_type, dj_exc_value, traceback)
File /usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/db/backends/util.py,
line 53, in execute
return self.cursor.execute(sql, params)
django.db.utils.ProgrammingError: column diffviewer_filediff.diff_hash_id
does not exist
LINE 1: ...CT COUNT(*) FROM diffviewer_filediff WHERE NOT (diffviewe...
What operating system are you using? What browser?
Scientific Linux release 6.3 (Carbon)
Please provide any additional information below.
The issue is similar to the one addressed here:
https://github.com/reviewboard/reviewboard/commit/11a850ca279416feed96beae9efd6c4c1f188f15
In fact, you only need to additionally catch a
django.db.utils.ProgrammingError in the except block and everything works
like a charm.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
You received this message because you are subscribed to the Google Groups
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.
Re: Issue 3499 in reviewboard: on submitting the RB request, i am seeing internal server error 500 (my username sushilk)
Updates: Status: Invalid Comment #1 on issue 3499 by trowb...@gmail.com: on submitting the RB request, i am seeing internal server error 500 (my username sushilk) http://code.google.com/p/reviewboard/issues/detail?id=3499 We need you to answer all the questions in the form. If you're just a user of the server (rather than the administrator), you may want to follow up with your local admins first. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Issue 3501 in reviewboard: djblets references cloudflare cdn
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 3501 by josh.guf...@gmail.com: djblets references cloudflare cdn http://code.google.com/p/reviewboard/issues/detail?id=3501 I run reviewboard behind a firewall, and references to cloudflare cause a few parts of the site to fail. What version are you running? 2.0.4 (djblets 0.8.7) What's the URL of the page containing the problem? admin/extensions/ What steps will reproduce the problem? 1. load the extensions page behind a firewall What is the expected output? What do you see instead? The list of extensions loads; instead i see an ajax spinner and javascript errors Backbone is not defined and Djblets.ExtensionManager is not a constructor What operating system are you using? What browser? RHEL 6/firefox 30 Please provide any additional information below. the files djblets/util/templates/js/underscore|backbone.html are trying to load data from cloudflare. I manually copied the js files to a static location on my webserver, edited those files to point to the new static files, and then regenerated static files. After that, the extension page loads correctly. https://github.com/djblets/djblets/blob/master/djblets/util/templates/js/underscore.html#L1 -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: Issue 2989 in reviewboard: Administrator not able to reopen review request after discard
Updates: Status: Fixed Owner: chip...@gmail.com Labels: Milestone-Release1.7.x Comment #2 on issue 2989 by chip...@gmail.com: Administrator not able to reopen review request after discard http://code.google.com/p/reviewboard/issues/detail?id=2989 Fixed on release-1.7.x (d513ba1) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: Issue 3500 in reviewboard: Update from RB 1.6.2 to 2.0.3 failed.
Updates: Status: Fixed Owner: chip...@gmail.com Labels: Milestone-Release2.0.x Project-ReviewBoard Component-RB-Site Comment #1 on issue 3500 by chip...@gmail.com: Update from RB 1.6.2 to 2.0.3 failed. http://code.google.com/p/reviewboard/issues/detail?id=3500 Fixed on release-2.0.x (c816421). This will go into 2.0.5. Thanks! -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: Issue 3402 in reviewboard: Include revision of the commits shown in the repository listing of a branch
Updates: Status: Fixed Comment #3 on issue 3402 by trowb...@gmail.com: Include revision of the commits shown in the repository listing of a branch http://code.google.com/p/reviewboard/issues/detail?id=3402 Fixed in release-2.0.x (bdf9343). Thanks! -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: Issue 3453 in reviewboard: can't discard draft
Updates: Status: Fixed Comment #6 on issue 3453 by trowb...@gmail.com: can't discard draft http://code.google.com/p/reviewboard/issues/detail?id=3453 OK, I determined that there's a problem whereby if the server responds with an error, then it would fail silently. I've fixed the error display in release-2.0.x (8ac72ed), which will ship in 2.0.5. That said, there's some cause for the error, which I still don't know. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
