Congratulations for finding the bug... :) This should be fixed now, it'll be live after our next production build.