This seems to be a bug, and we are already investigating the possible cause for this issue. We'll try to patch it asap
