Skip to content
Discussion options

You must be logged in to vote

@mhonorio thanks for raising this. We've fixed this, you can check the details in the original issue, #9661

The fix is present in the most recent edge at the time of writing (edge-22.10.3), and will likely be shipped in the next stable-2.12.3 release.

Replies: 1 comment 2 replies

Comment options

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

@seagullua
Comment options

Answer selected by mhonorio
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants