Skip to content
Discussion options

You must be logged in to vote

Just calling out that since the update to 0.16.0 I have not yet had this issue re-occur, despite it regularly happening with 0.15.0. So I'm hopeful that something with that release resolved this issue.

Replies: 2 comments 19 replies

Comment options

NickM-27
Apr 28, 2025
Collaborator Sponsor

You must be logged in to vote
18 replies
@JaggedJax
Comment options

@NickM-27
Comment options

NickM-27 Jul 15, 2025
Collaborator Sponsor

@JaggedJax
Comment options

@NickM-27
Comment options

NickM-27 Jul 15, 2025
Collaborator Sponsor

@JaggedJax
Comment options

Comment options

You must be logged in to vote
1 reply
@JaggedJax
Comment options

Answer selected by JaggedJax
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment