[@drwebbe Participant 3 years, 3 months ago]

I created a ticket in the bugtracker

[@drwebbe Participant 3 years, 3 months ago]

The error still exists in v10.3.0