Stephen Asbury

I am open to the idea, but also don't want to bring in a new library/dependency, perhaps we could do a blog post/doc example instead?

i merged your pull request into 2.2.4, once that ships we can close this.

Probably overkill, I don't think it get the exception again.

2.2.0 will also include a tracing option that may help with this

Just noticed this. The code changed in 2.0, do you still see the problem? We may have to make a new PR or I can just fix if you still...

Eventually....