Thanks for the report, and I think it should be fixed in the next public version (which is ~2-3 weeks away, depending on how soon beta is over).
