Hello maintainers,

The bug was caused by a mistake on my end (confusing version 2.6.3 with 3.0.0). 
Please consider this issue closed.

Best,
Rovol


Reply via email to