This is fixed only in the upcoming version 0.4.2 which will be released in the next few days, I hope.
This is fixed only in the upcoming version 0.4.2 which will be released in the next few days, I hope.