streaming-api-connection doesn't forward twitter api errors

[mikedotalmond]

I recently started getting 413 responses from the statuses/sample streaming endpoint, but I had to put some logs into streaming-api-connection.js to find that out. The error code I get from twit is just the "incorrect header check" one from gzip when it recives uncompresed data.

Incidentally, my code hasn't changed and I started getting these errors yesterday... so I'm not sure why it's happening, unless twitter has changed something.

[patrikhermansson]

Same here.

[dandv]

The streams implementation in twitter-lite does forward errors. Here's a failed Travis test due to rate limiting.