This seems to be a bug. We are currently investigating a possible cause of it, and we'll try to release the fix asap!
