anaconda upload fails silently if the user's storage limit is exceeded

[stuarteberg]

When a user's storage limit for anaconda.org is exceeded, anaconda upload fails. Fair enough! :-)

But it would be nice to see an error message. There is no obvious clue that the upload failed, unless you notice that the Upload complete message wasn't printed, or if you happen to check the exit code. Here's what you see:

$$ anaconda upload -u flyem-forge /miniforge/conda-bld/noarch/flyemflows-0.0.post.dev171-py_0.tar.bz2
Using Anaconda API: https://api.anaconda.org
Using "flyem-forge" as upload username
Processing '/miniforge/conda-bld/noarch/flyemflows-0.0.post.dev171-py_0.tar.bz2'
Detecting file type...
File type is "conda"
Extracting conda package attributes for upload
Creating package "flyemflows"
Creating release "0.0.post.dev171"
Uploading file "flyem-forge/flyemflows/0.0.post.dev171/noarch/flyemflows-0.0.post.dev171-py_0.tar.bz2"

$$ echo $?
1

cc @tingzhao

[stefdoerr]

Yes please! I just spent 3 hours trying to figure out why it would not upload.

[bkreider]

This is very similar to #501. It looks it fails at a slightly different spot, but I'm betting it is not catching the exception like the problem in #501 and then the stack trace gets eaten at the cli level.