Thanks for the report. You are correct that this was introduced by a recent change in 2.1.12rc1 and it is now fixed for the next release.
Thanks for the report. You are correct that this was introduced by a recent change in 2.1.12rc1 and it is now fixed for the next release.