The existing behavior on hangups and aborts disregarded the parameters passed in via options, and failed at a number smaller than maxRetries. This is counter intuitive, undocumented, and not modifiable from the external API. This pull request defaults maxHangups and maxAborts to maxRetries and changes the underlying code to actually use those values rather than hard coded values.
For v0.10 we need to check `req.timedOut` in `gotEnd()` to know that we aborted, and this is not a complete response.
… the timing event. Fixes #10
when the filtered counter was added I failed to account for it in setPending and resetCounters. This caused the pending count to not be calculated correctly, it was exactly filtered count too large. In the future it may be better to use a single counter for pending that is incremented on 'request' and decremeted on 'complete'