Thanks for reporting this. We are already working on adding a fix to this. It should be handled in the next few days