Thank you for bringing this to our attention, @Marius!
This has been fixed with 1.2.9.9.4. Kindly let me know if this is the case on your end.
Thank you.