somewhat more detailed error messages

[dominykas]

With 2.0.3 I started seeing a lot of unknown in my error logs - that's not good, as it's really tricky to filter these errors out, so I changed the messages to, um, include more words :)

Speaking of 2.0.3 - how come npm has it, but the master here is still 2.0.1?

[naugtur]

2.0.3 is here, I didn't see that a push failed (probably made a typo in key password)

Your change also seems to cover for #88
I'll look into it soon.

[dominykas]

Rebased to latest

[naugtur]

https://github.com/Raynos/xhr/pull/89/files#diff-168726dbe96b3ce427e7fedce31bb0bcR156 is great, I'm a bit worried about changing the existing error message.

But I'll merge it soon.
Anyone wants to comment?

[mattdesl]

I am 👍 on this, the error message "unknown" doesn't really tell us much.

[dmlap]

Any chance timeouts could also be indicated in a way that's easy to distinguish programmatically? I never finished putting together use-cases for #88 but it's still an important situation to recognize for us. I could parse it out of the error message after this PR but that seems like abusing the API a bit to me.

[naugtur]

I'm on vacation (and have been for a while) with limited access to Internet and my private keys, I'll get back to this soon. If we're upgrading error messages, I want to make sure #88 is addressed fully