jaromirk opened this issue 3 years ago · 3 comments
Acknowledging. I'll try to sort out what could be going on shortly. This one looks simple.
Fix will be in the next push.
This is fixed in 2.0.2.