Hey Kunpeng, The issue has already been reported a couple of times and will be fixed in the upcoming 1.5 RC.
Best regards, timmse