Version: 1.13.2
Version 1.10 didn’t have this problem. This problem was discovered after upgrading to 1.13.2.