Closed shawndrost closed 9 years ago
Thank you! We'll check it out. :boom: :heart:
So it shouldn't reach an exception path since we catch the urllib HTTPError and then set state accordingly in the APIResponse. We'll have to test this.
Sorry this took so long. We've found the root cause of these issues and fixed it in the latest release. Thanks for telling us about it.
The code path I moved in this commit will not be reached AFAICT -- the server returns a 400 and reaches the exception path instead. I've moved it and probably created other problems. However, I can promise that currently, creating a repo with a
/
in it results in the error message "400 BAD REQUEST" and not "don't use that character".(I haven't tested this... sorry! Hope this PR is useful anyway.)