Thank you for reporting. This is already fixed and you’ll get it with the next release after 4.3.0. Unfortunately the fix didn’t catch 4.3.0 release.
Thank you for reporting. This is already fixed and you’ll get it with the next release after 4.3.0. Unfortunately the fix didn’t catch 4.3.0 release.