Hacker News new | ask | show | jobs
by spullara 1793 days ago
It was fixed a long time and only closed recently, see the message from the dev.
1 comments

No, the dev writes on GitHub that "this issue was fixed in 5.17 (which hit 100% production on 7/21)". Releases show 5.17.0 was released on July 15. They've also linked the commits that fix the bug - the fixes were committed 10 days ago.