Thanks for reporting this @rliang. We are looking into investigating this and will soon add a fix for this.