I believe I found the source of the error. Thanks for reporting it! It’ll be patched in the next hotfix (v0.9.3)
