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.

Reply via email to