@danielnk I don't think we'll be able to address this issue without addressing this post's issue, since the root of this problem is the same as that post.
That said, we acknowledge the severity of the issue and will revert as soon as possible on a potential solution.