Hi @alexander,
We’ll provide a fix for this in 1.6 stable.
Original post that’s already marked as work-in-progress: