Thread

Hey, thanks for the report. We were able to reproduce this issue successfully. We'll implement a fix for this in the next build.