Error while adding a comment to the diff

2010-12-22 Thread orzha1
Hello, I'm facing a strange issue.When trying to add a comment to the code the following occurs: 2010-12-22 17:41:27,912 - DEBUG - Generating diff viewer page for filediff id 14 2010-12-22 17:41:27,916 - DEBUG - Begin: Generating diff file info for diffset id 14 2010-12-22 17:41:27,922 - DEBUG -

Re: Permissions and Offline Mode

2010-12-22 Thread Leonel Togniolli
Hi Christian, Yes. Admin UI - Settings - Authentication - Allow anonymous access (or something like that). Thanks, this works. Missed it the first time around. This is a requirement. Review Board grabs the files from the SCM and patches them in order to get the complete original and new

Re: Reversed (or previously applied) patch detected! when view diff after git push

2010-12-22 Thread David Birdsong
On Tue, Dec 21, 2010 at 6:24 PM, Christian Hammond chip...@chipx86.com wrote: Can you plug in a filename and SHA1 into that raw URL mask and see if it's actually fetching using the SHA1? If modifying the tip of origin breaks things, I wonder if it's not actually making use of the SHA1 on your

Re: Reversed (or previously applied) patch detected! when view diff after git push

2010-12-22 Thread Christian Hammond
It's the SHA1 of the commit. I think I saw a setup once before that required id= instead of id2=. Maybe try that. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Wed, Dec 22, 2010 at 11:37 AM, David

Re: Reversed (or previously applied) patch detected! when view diff after git push

2010-12-22 Thread David Birdsong
On Wed, Dec 22, 2010 at 4:38 PM, Christian Hammond chip...@chipx86.com wrote: It's the SHA1 of the commit. but git log shows a different commit id for that commit. referring to that hash tag when performing a diff, does work though git diff 9455e4714fa626cbd8410a3d13abb3bbe7a79f8c file_name diff

Django security advisory

2010-12-22 Thread Christian Hammond
Hello everyone, The Django project today announced two newly discovered security vulnerabilities and an accompanying update, which recommend everyone updates to. To update to the latest Django release (1.2.4), use: easy_install -U Django If you're running 1.1.x and don't wish to upgrade to