SamHoque opened this issue 9 months ago · 1 comments
Hi @SamHoque . Thanks for reporting. This should be fixed in release v2.5.0.