Re: Issue 1975 in reviewboard: Git rbssh:bad line length character

2011-03-13 Thread reviewboard

Updates:
Status: Incomplete

Comment #5 on issue 1975 by trowb...@gmail.com: Git rbssh:bad line length  
character

http://code.google.com/p/reviewboard/issues/detail?id=1975

(No comment was entered for this change.)

--
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To post to this group, send email to reviewboard-issues@googlegroups.com.
To unsubscribe from this group, send email to 
reviewboard-issues+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/reviewboard-issues?hl=en.



Re: Issue 1975 in reviewboard: Git rbssh:bad line length character

2011-02-07 Thread reviewboard


Comment #4 on issue 1975 by anthony@gmail.com: Git rbssh:bad line  
length character

http://code.google.com/p/reviewboard/issues/detail?id=1975

Fair enough.  I am glad that I already switched over to ubuntu but just  
wanted to provide feedback on 1.5.3 since I still have the windows install  
available.  With it strongly being recommended to be run on linux you could  
probably deploy a app VM to help adoption if you haven't already.


--
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To post to this group, send email to reviewboard-issues@googlegroups.com.
To unsubscribe from this group, send email to 
reviewboard-issues+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/reviewboard-issues?hl=en.



Re: Issue 1975 in reviewboard: Git rbssh:bad line length character

2011-02-07 Thread reviewboard


Comment #3 on issue 1975 by chip...@gmail.com: Git rbssh:bad line length  
character

http://code.google.com/p/reviewboard/issues/detail?id=1975

Unfortunately, due to the way STDIN/STDOUT piping is handled on Windows (in  
particular with Python) it is extremely difficult to get 100% right, and  
likely will depend on where each piece of the puzzle is coming from  
(cygwin, native installers, etc.) and how things are invoked. It truly is a  
pain, and I think from here on out we're going to have to push harder for  
Linux-based installs.


Our new unit tests for this add a repository and check it, and these do  
pass on Windows, but again, it could be a number of things.


So in theory, you can enable debugging. It's designed to work on a  
developer install right now, so I'm actually not completely sure where the  
log file will go (hopefully in data/). We'll need to sort that out down the  
road.g


You can enable this by setting DEBUG_RBSSH=1 in the environment (probably  
in your Apache config). It should spit out a rbssh.log file. It'll be going  
in the current working directory, whichever that is when it's executed. You  
may have to search around.


Alternatively, you can always edit reviewboard/cmdline/rbssh.py,  
find "rbssh.log" and give it a custom path for now.


--
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To post to this group, send email to reviewboard-issues@googlegroups.com.
To unsubscribe from this group, send email to 
reviewboard-issues+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/reviewboard-issues?hl=en.



Re: Issue 1975 in reviewboard: Git rbssh:bad line length character

2011-02-07 Thread reviewboard


Comment #2 on issue 1975 by anthony@gmail.com: Git rbssh:bad line  
length character

http://code.google.com/p/reviewboard/issues/detail?id=1975

I didn't have this problem on 1.5.2 because on 1.5.2, RB/rbssh would hang  
after the EOF in transport thread log line


It's a bit tricky for me to answer your question about cygwin or not.   
Cygwin is installed but I had installed python as "native" for windows  
through their redist.  I'm not sure if it's executing in the context of  
cygwin by default.  I installed git as a package for windows as well.


In my command prompt when I run which git, which python they reference  
cygdrive


The bad line length error is followed by a randompool_Deprecation warning  
which references my python install without cygdrive so I don't think it's  
running in the context of cygwin.


Is there some logging I can add to rbssh to definitively figure it out?

--
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To post to this group, send email to reviewboard-issues@googlegroups.com.
To unsubscribe from this group, send email to 
reviewboard-issues+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/reviewboard-issues?hl=en.



Re: Issue 1975 in reviewboard: Git rbssh:bad line length character

2011-02-07 Thread reviewboard

Updates:
Status: NeedInfo
Owner: chipx86
Labels: OpSys-Windows Component-SSH

Comment #1 on issue 1975 by chip...@gmail.com: Git rbssh:bad line length  
character

http://code.google.com/p/reviewboard/issues/detail?id=1975

Did you have this problem on 1.5.2?

Our tests should have caught this on Windows, but it may very well depend  
on whether you're using cygwin git, or something else.


Can you tell me where your git comes from, and whether you're using Cygwin  
for Python or anything else?


--
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To post to this group, send email to reviewboard-issues@googlegroups.com.
To unsubscribe from this group, send email to 
reviewboard-issues+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/reviewboard-issues?hl=en.