#4755 git-cl issues

[Phil Holmes]

Urs Liska reported that git-cl crashes when the Allura tracker times out. This is the relevant traceback:

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):
Traceback (most recent call last):
File "/home/uliska/git/lilypond/git-cl/git-cl", line 628, in <module>
sys.exit(main(sys.argv))
File "/home/uliska/git/lilypond/git-cl/git-cl", line 622, in main
return func(argv[2:])
File "/home/uliska/git/lilypond/git-cl/git-cl", line 341, in CmdUpload
issueId = projecthosting_upload.upload(issue, patchset, subject,
desc, issueId)
File "/home/uliska/git/lilypond/git-cl/projecthosting_upload.py", line
182, in upload
status = patchy.upload(issue, patchset, subject, description, issue_id)
File "/home/uliska/git/lilypond/git-cl/projecthosting_upload.py", line
175, in upload
issue_id = allura_issues.create_issue(subject, description)
File "/home/uliska/git/lilypond/git-cl/allura_issues.py", line 25, in
create_issue
allura_result = urllib.urlopen (allura_api + "/new", data_encoded)</module>

[...]
IOError: [Errno socket error] [Errno 110] Connection timed out

[Phil Holmes]

Federico made further suggestions:

As you can see below, there are two default configuration options that
are missing ([] is empty):

1. Allura server
2. CC list

Adding the Allura server would be convenient.
I'm not sure what the CC list is for, as the email to the dev list is
sent when the rietveld issue is published on the web interface.

$ 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/) []:
xxxxxxxxxxxxxx
CC list: