I tested with v1.0.0-beta.1.
was this covered by: #1142 or is are their more?
This results are run on #1142.
This issue is still left.
@tricknotes do you know the root cause?
@wycats Sorry to my slow response.
No. I don't know why this error caused.
It seems that this issue was fixed by recent commits.