gt; *Sent:* Friday, February 01, 2013 4:13 AM
> *To:* reviewboard@googlegroups.com
>
> *Subject:* Re: a couple of issues post 1.7.1 upgrade
>
> ** **
>
> I am also seeing this issue. Did you ever find a solution for this?
>
> ** **
>
> - Loke
>
> On Monda
board@googlegroups.com [mailto:reviewboard@googlegroups.com]
> *On Behalf Of *Loke Dupont
> *Sent:* Friday, February 01, 2013 4:13 AM
> *To:* reviewboard@googlegroups.com
>
> *Subject:* Re: a couple of issues post 1.7.1 upgrade
>
> ** **
>
> I am also seeing thi
legroups.com [mailto:
> revie...@googlegroups.com ] *On Behalf Of *Christian Hammond
> *Sent:* Friday, January 04, 2013 2:48 PM
> *To:* revie...@googlegroups.com
> *Subject:* Re: a couple of issues post 1.7.1 upgrade
>
>
>
> So that function is doing basically a 'svn cat&#
the key.
From: reviewboard@googlegroups.com [mailto:reviewboard@googlegroups.com]
On Behalf Of Christian Hammond
Sent: Friday, January 04, 2013 1:32 PM
To: reviewboard@googlegroups.com
Subject: Re: a couple of issues post 1.7.1 upgrade
Did you ever have anything filled out in the Passwo
though and
>> have the same results.
>>
>> ** **
>>
>> I was able to use svn cat successfully as www-data with the key.
>>
>> ** **
>>
>> ** **
>>
>> *From:* reviewboard@googlegroups.com [mailto:reviewboard@googlegroups.com]
>> *On Behalf Of
o use svn cat successfully as www-data with the key.
>
> ** **
>
> ** **
>
> *From:* reviewboard@googlegroups.com [mailto:reviewboard@googlegroups.com]
> *On Behalf Of *Christian Hammond
> *Sent:* Friday, January 04, 2013 1:32 PM
>
> *To:* reviewboard@goo
, 2013 1:32 PM
To: reviewboard@googlegroups.com
Subject: Re: a couple of issues post 1.7.1 upgrade
Did you ever have anything filled out in the Password field for the
repository? Do you still have the username field set? If these were ever
filled out, be sure they're filled out now (re-typ
*Christian Hammond
> *Sent:* Thursday, January 03, 2013 10:16 PM
>
> *To:* reviewboard@googlegroups.com
> *Subject:* Re: a couple of issues post 1.7.1 upgrade
>
> ** **
>
> If it's process_stdin, it sounds like it's svnserve asking for the
> password, meaning the SSH aut
Subject: Re: a couple of issues post 1.7.1 upgrade
If it's process_stdin, it sounds like it's svnserve asking for the
password, meaning the SSH authentication was successful. I assume it's
doing this in the original log you showed as well, and the lack of stdin
was causing the c
t; password, if that's what is actually happening.
>
> > -Original Message-
> > From: reviewboard@googlegroups.com
> > [mailto:reviewboard@googlegroups.com] On Behalf Of Christian Hammond
> > Sent: Thursday, January 03, 2013 5:45 PM
> > To: review
ooglegroups.com] On Behalf Of Christian Hammond
> Sent: Thursday, January 03, 2013 5:45 PM
> To: reviewboard@googlegroups.com
> Subject: Re: a couple of issues post 1.7.1 upgrade
>
> At what point during the log is it asking for the password?
>
> It looks like it's connected
t INFO Secsh channel 1 opened.
> 01-04 01:29 root DEBUG!!! Using PosixHandler
> 01-04 01:29 root DEBUG!!! Sending command ['svnserve',
> '-t']
> 01-04 01:29 paramiko.transport DEBUG[chan 1] Sesch channel 1 request
> ok
> 01-
;,
'-t']
> -Original Message-
> From: reviewboard@googlegroups.com
> [mailto:reviewboard@googlegroups.com] On Behalf Of Christian Hammond
> Sent: Thursday, January 03, 2013 1:31 PM
> To: reviewboard@googlegroups.com
> Subject: Re: a couple of issues post 1.7.1 upgr
Hey Christian,
Here is the data
Thanks again,
Dave
>From reviewboard.log
2013-01-02 07:47:46,446 - DEBUG - Generating diff viewer page for filediff
id 717
2013-01-02 07:47:46,448 - DEBUG - Begin: Generating diff file info for
diffset id 717
2013-01-02 07:47:46,455 - DEBUG - End: Generating
Hi Dave,
Hard to say what this may be caused by without some additional debug info.
Would you mind checking and providing two things:
1) Any relevant section from reviewboard.log after the attempt.
2) JavaScript debug logs from the page when the buttons are disabled (easiest
with Chrome or Fire
15 matches
Mail list logo
