I have double checked and this issue will indeed be resolved by the next release of 6.1 (6.1.7) and by version 6.2.0 which will be available in the near future.

Thanks for reporting the issue and providing an example!