Thank you for the heads up! The issue has been resolved in 0.4.2, we can’t wait for you to give it a try!
