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