Howdy, I upgraded to the newest version 4.7.0 and started getting the error described in issue #105 again. I downgraded back to 4.6.2 and haven't seen the issue pop up. Maybe the fix was not properly merged to later versions?
@Charles101993 I'm not able to reproduce this in 4.7.0. Can you send the request you are making (if you still have it, I know you wrote this about 4 months ago)?
Howdy, I upgraded to the newest version 4.7.0 and started getting the error described in issue #105 again. I downgraded back to 4.6.2 and haven't seen the issue pop up. Maybe the fix was not properly merged to later versions?