I can confirm that this bug is fixed as of the latest public release. It was a very frustrating bug; thank you for addressing it.
