Hi @charceypetersen
we are not aware of the bug. We did release a minor version on Feb 16. but after checking the diff it does not seem like anything was changed directly.
Could you provide more information, we are especially interested in your input and in the stack trace of the exception so that we can pinpoint the problem. You can also report the issue here
Ah, i just saw your edit that you are on version 3.8.2.
There indeed was a change from 3.8.1 to 3.8.2 that could cause that issue. We will investigate.