Yes, we pushed a fix specific to this on Tuesday. If you are on the latest and still seeing the issue, please reply.
