I see that this was fixed in v2.1.10, but I am on v2.1.11 and the issue is present today.  