Thank you for that report. The fix for it has been pushed to the next Pre-Release (3.0.19/2.2.99). Please give it a try.
See you Michael.