however I’m running against this issue [KT-48918] which seems to be fixed in
1.5.31
. Does someone have any insight about it?
r
Richard Gomez
10/11/2022, 2:16 PM
If no one has anything to say about this, I'd recommend commenting on the issue with the information of what you're experiencing. Perhaps open a new issue as well.