Hi @kata7,
Thank you for bringing this to our attention. We have reproduced the bug in version v0.5.8.166 and are currently working on a fix. We appreciate your patience as we resolve this issue.
