Ok.
We'll just skip the review on this one change.
Thanks for your help!
John
On Fri, May 24, 2013 at 4:51 PM, Christian Hammond wrote:
> Hi,
>
> I don't know. It's not our timeout. That's pretty much an unmanageably
> long diff though, and you're going to hit other issues with it as well (not
Hi,
I don't know. It's not our timeout. That's pretty much an unmanageably long
diff though, and you're going to hit other issues with it as well (not the
least of which is review time).
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, In
Christian,
Looks like it is a timeout.
There are only 9 changesets in the repo (it's a new one) and rev 4 is in
fact a big change.
I used the used the incorrect command to do the diff (hg diff -r 4). The
correct mercurial command is
hg diff -c 4 | wc
136638 672689 5040973
(Sorry for th
Okay. Well, the stack trace indicates it has to do with reading the uploaded
file. There's an I/O error at some point reading that. I wouldn't be able to
say why without some extensive debugging in there.
I should point out that this is all inside Django code where this loading is
happening, an
No, it's quite small:
hg diff -r 4 | wc
106 5393737
On Fri, May 24, 2013 at 3:00 PM, Christian Hammond wrote:
> How big is the diff you're trying to upload? Could it be just too large
> and timing out?
>
> Christian
>
> --
> Christian Hammond - chip...@chipx86.com
> Review Boar
How big is the diff you're trying to upload? Could it be just too large and
timing out?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On Fri, May 24, 2013 at 2:40 PM, J Arrizza wrote:
> Hi Christian,
>
Hi Christian,
I fixed the directory owner to be -R www-data:www-data (it was incorrect).
I deleted the current reviewboard.log
I pressed "Save" in the Logging Settings
I redid the hg postreview
Here is the complete log
cm5@cm5:/fmcapps/log$ cat reviewboard.log
2013-05-24 21:36:58,071 - INFO - -
Hi,
Can you check to see what reviewboard.log says when doing this?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On Fri, May 24, 2013 at 2:25 PM, J Arrizza wrote:
> We recently upgraded from RB 1.7 B
We recently upgraded from RB 1.7 Beta 1 to 1.7.7.1 and are now getting
Internal Server Errors on one repository, see below for the traceback.
- Posting a review creates an empty review, i.e. no diffs.
- I can create reviews with diffs in other repositories. Only one repo (so
far) that is failing.
When I try that, the admin web interface says:
"Unable to authenticate against this repository using one of the supported
authentication types."
- Peter
On Friday, May 24, 2013 5:08:45 PM UTC-4, David Trowbridge wrote:
> In the repository configuration, you'll want to set your path to
> sne
In the repository configuration, you'll want to set your path to
snelling@172.16.27.63:/localdisk/git/repositories/TCD.git and the raw file
url to the gitweb url that you currently have as the path.
-David
On Fri, May 24, 2013 at 1:53 PM, Peter Snelling
wrote:
> I've just installed ReviewBoard
I've just installed ReviewBoard 1.7.7.1 on a Suse linux server (with git,
apache, postgresql, modswgi, memcached, ...).
I had some trouble adding our central git repository using the admin web
interface. What finally seemed to work was using a gitweb interface to our
repository. I set the Path
Nothing has been actively worked on until recently. We're working on some
reporting functionality, which we'll probably make available under a
commercial license (in order to fund the project). If you'd like to be
notified when we make that available, we'll post on this list, but our
announcements
Hello,
What ever came of the statistics extension that was being worked on a
couple/few years ago? Is it available in some location for the current
ReviewBoard release?
Thanks!
-Chad
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Le
I would never have guessed that. ever!
let me see what I can do to maybe rename this machine and see if the issue
is cleared up.
thank you much for your insight!!
On Fri, May 24, 2013 at 2:58 PM, Christian Hammond wrote:
> The reason is that "_" is not valid in hostnames. Django sees that and
The reason is that "_" is not valid in hostnames. Django sees that and
assumes something bad is happening.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On Fri, May 24, 2013 at 7:57 AM, Ryan Guilbault wr
interestingly, after removing ALLOWED_HOSTS and even switching back to
DEBUG = False, I'm getting back:
['*']
from running the lines you recommended. here is my settings_local.py file:
# Site-specific configuration settings for Review Board
> # Definitions of these settings can be found at
> #
Hi,
If ALLOWED_HOSTS is not set, you shouldn't see this, unless you're
accessing it with a domain that Django doesn't consider to be a validly
formed domain. It will first check the "Host:" header (as sent by the
client) and, if that's missing, the server name as reported by mod_wsgi.
It would he
hi Christian.
The error is the same as with 1.6.3.
2013-05-02 12:34:10,206 - DEBUG - - starting thread (client mode):
0x2f88e250L
2013-05-02 12:34:10,453 - INFO - - Connected (version 2.0, client
OpenSSH_4.3)
2013-05-02 12:34:10,697 - DEBUG - - kex
algos:['diffie-hellman-group-exchange-sha1
19 matches
Mail list logo
