Thanks for the report, Litmirskiy – this is indeed a known issue and has been added here for tracking:
No further details required, but we appreciate the effort!