Forums
(@schitkowski)
3 weeks, 5 days ago
Can confirm: The issue is still there after v3.25.2 release.