In 2025 (version 24.3.4), there is a similar problem, and the solution was described in an issue on their GitHub repo.
Steps: