Thanks Josh for posting the fix. This bug appeared on my testing system before and somehow it made its way to the release. Will deploy the fix tomorrow.