Re: Allure and git-cl troubleshooting

[Paul Morris]

Hi Trevor,

You’re right.  I also just looked closer at the traceback and at the function 
_GetAuthToken in git-cl/upoad.py where things go wrong (line 262).  The doc 
string says that function raises a ClientLoginError for authentication 
problems, and an HTTPError for "some other form of HTTP error”.  And the 
traceback I got ends with an HTTPError, namely 404 not found.  So it sounds 
like it’s may not be a problem with the authentication with google per se, but 
with connecting with google in the first place.

-Paul

> On Oct 26, 2015, at 3:29 PM, Trevor Daniels <address@hidden> wrote:
> 
> Hi Paul
> 
> Looking at the error again it seems to be a problem with authenticating at 
> GoogleCode rather than Allura at SourceForge.
> 
> Trevor
> 
> ----- Original Message ----- 
> From: "Paul Morris" <address@hidden>
> To: "James" <address@hidden>
> Cc: "Phil Holmes" <address@hidden>; "Trevor Daniels" <address@hidden>; 
> "lilypond-devel" <address@hidden>
> Sent: Monday, October 26, 2015 6:15 PM
> Subject: Re: Allure and git-cl troubleshooting
> 
> 
> Thanks Trevor, Phil, and James.  I believe I have everything configured 
> correctly.  (I removed my bearer token below, but I just double checked and 
> it’s correct.)
> 
> [lilypond-git (whiteout-style)]$ git cl config
> Rietveld server (host[:port]) [codereview.appspot.com]: 
> Allura server [https://sourceforge.net/p/testlilyissues/issues/]: 
> Allura bearer token (see https://sourceforge.net/auth/oauth/) 
> [***REMOVED***]: 
> CC list ("x" to clear) address@hidden: 
> 
> -Paul