Closed leshalv closed 9 months ago
Thanks, looking into it.
Ok, I've released v0.15.5
which just reverts to v0.15.3 which should fix this problem.
I'm going to leave this issue open for now so other folks see it if they run into it, but this should be fixed as of v0.15.5
. Let me know if you see otherwise please.
v0.15.5 effective
This error occurs with the new version