Skip to content
Discussion options

You must be logged in to vote

@TheFlameFish:
Thank you for reporting this. 😊👌
I believe this bug was introduced with version 0.23.0, and I made a fix for it with the next version 0.23.1.

A temporary work-around would be to stick to use version 0.22.2 until the next version is out, which does not have this bug.

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@TheFlameFish
Comment options

@flemming-n-larsen
Comment options

Answer selected by TheFlameFish
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants