Finally, it has been fixed. The fix will go to the upcoming v2.3 release.