Hi ,
I am happy to report that this has already been fixed internally and is scheduled to be released in 4.13.