Closed AmlingPalantir closed 7 years ago
0.8.1 is available now and includes the fix for this if you want to try it out.
We've picked it up, although we were not producing the error 100% of the time so I can't strictly verify it's fixed. Anyway, I'll assume it is until/unless I see it again.
Good catch, thanks. This should be fixed by #54. I'll try to release 0.8.1 later today or tomorrow.