Yes we are aware of this issue, we have a ticket about it internally, we will try to fix it in January.