Open zebulasampedro opened 6 years ago
The request logic seems to protect against this, and I can't reproduce it under test, but it very clearly happened. My suspicion is that another error broke normal execution flow and resulted in this occurrence, given that we were observing other request problems around the same time.
I'm going to bump this from the next release for now, but keep it open and continue monitoring. In the future, this is the kind of problem that will be mitigated by #327.