@drwebbe
1 year, 10 months ago
I created a ticket in the bugtracker
The error still exists in v10.3.0