Reviewbot: Should I see cppcheck and pep8 in my extension list?

2013-09-25 Thread Steve
I installed reviewbot on our 1.7.14 server using these instructions: https://github.com/reviewboard/ReviewBot It looks like pep8 and cppcheck are automatically installed with reviewbot, but I don't see them listed in the extension list. I'm looking for them under *Extensions - Database -

Re: Reviewbot: Should I see cppcheck and pep8 in my extension list?

2013-09-25 Thread Steven MacLeod
Right after the section you've pasted, you'll see this: After a tool has been installed on a worker, it must be registered with the Review Bot extension, and configured in the admin panel. Registering tools is accomplished in the following manner: 1. Go to the extension list in the admin

Re: Reviewbot: Should I see cppcheck and pep8 in my extension list?

2013-09-25 Thread Steve
Sorry, I should have mentioned that I did that. I even restarted apache and did the refresh again. I'm still not seeing any extensions. --Steve On Wednesday, September 25, 2013 11:24:22 AM UTC-7, Steven MacLeod wrote: Right after the section you've pasted, you'll see this: After a tool

Re: Reviewbot: Should I see cppcheck and pep8 in my extension list?

2013-09-25 Thread Steve
This may be the problem. I'm running the reviewbot worker as apache and seeing this error: [2013-09-25 10:57:33,786: WARNING/MainProcess] There was an error while creating a cookie file: [Errno 13] Permission denied: 'reviewbot-cookies.txt' [2013-09-25 10:57:33,786: ERROR/MainProcess] Could

Re: Reviewbot: Should I see cppcheck and pep8 in my extension list?

2013-09-25 Thread Steve
Okay, I restarted the reviewbot work as root and now the extensions show up. The reviewbot-cookies.txt file was written into the directory where I cloned the reviewbot source, which was owned by root. I didn't expect that directory to be a working directory. That seems odd to me. On

Re: Issue 1426 in reviewboard: Reply on the diff page is confusing and error-prone.

2013-09-25 Thread reviewboard
Comment #13 on issue 1426 by sumee...@gmail.com: Reply on the diff page is confusing and error-prone. http://code.google.com/p/reviewboard/issues/detail?id=1426 the fix is to probably allow entering comments from the diff page. why should a user have to navigate to a different page and

Re: Issue 2356 in reviewboard: Got API Error 207 (HTTP code 400): The file was not found in the repository

2013-09-25 Thread reviewboard
Updates: Status: Incomplete Comment #3 on issue 2356 by trowb...@gmail.com: Got API Error 207 (HTTP code 400): The file was not found in the repository http://code.google.com/p/reviewboard/issues/detail?id=2356 (No comment was entered for this change.) -- You received this message

Re: Issue 2823 in reviewboard: Hosting account information doesn't stick

2013-09-25 Thread reviewboard
Updates: Status: ThirdParty Comment #4 on issue 2823 by trowb...@gmail.com: Hosting account information doesn't stick http://code.google.com/p/reviewboard/issues/detail?id=2823 The attached patch may fix it but it's also not quite correct. Given that this is only an issue in your

Re: Issue 2988 in reviewboard: Something broke! (Error 500) 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 repor

2013-09-25 Thread reviewboard
Updates: Status: Incomplete Comment #3 on issue 2988 by trowb...@gmail.com: Something broke! (Error 500) 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