Am 07.02.2016 um 15:07 schrieb Simon Albrecht:
> On 07.02.2016 14:50, Phil Holmes wrote:
>> I wasn't aware that git-cl "always fails".  Could you describe the
>> problem
> 
> I thought it was a known issue? It’s the case for which you recently
> added more helpful messages. Here’s the command line in- and output:
> 
> $ git cl upload origin/master
>  Documentation/changes.tely     | 18 ++++++++++++++++++
>  scm/define-markup-commands.scm | 10 ++++++++++
>  2 files changed, 28 insertions(+)
> Upload server: codereview.appspot.com (change with -s/--server)
> Your browser has been opened to visit:
> 
>     https://codereview.appspot.com/get-access-token?port=8001
> 
> If your browser is on a different machine then exit and re-run
> upload.py with the command-line parameter
> 
>   --no_oauth2_webbrowser
> 
> Issue created. URL: http://codereview.appspot.com/281710043
> Uploading base file for Documentation/changes.tely
> Uploading base file for scm/define-markup-commands.scm
> We were not able to associate this patch with a tracker issue.
> Please enter a valid tracker issue number
> (or enter nothing to create a new issue):
> Error code 403
> Failed URL was http://sourceforge.net/rest/p/testlilyissues/issues//new
> Failed data was
> ticket_form.summary=Add+%5Cwith-dimensions-from+markup+command&ticket_form.custom_fields._patch=new&ticket_form.custom_fields._type=Enhancement&ticket_form.description=Add+%5Cwith-dimensions-from+markup+command%0A%0AThis+command+acts+as+a+front-end+to+%5Cwith-dimensions%2C%0Ataking+the+new+dimensions+from+a+markup+object+instead+of%0Ahaving+them+explicitly+given.%0AAlso+provides+a+Changes+entry.%0AI+didn%E2%80%99t+think+a+regtest+was+necessary%2C+since+the+functionality%0Aisn%E2%80%99t+new.%0A%0Ahttp%3A%2F%2Fcodereview.appspot.com%2F281710043&access_token=8f1c33f1a44226b74411&ticket_form.status=Started
> 
> 
>> and provide a traceback?
>>
>> I everyone having the same problem? 
> 
> IIRC, it has been reported by others, and Urs already posted a traceback
> – somewhere…

I definitely don't have *that* problem, and the traceback I posted was
surely something different. While I had network issues the connection
timed out, and git-cl didn't gracefully catch that exception.

Urs

> 
> HTH, Simon
> 
> _______________________________________________
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user


-- 
Urs Liska
www.openlilylib.org

_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to