Looks like it’s fixed on 5.1.
The Bug Tracker shared by @Sebatnik gives info about the commit and target version.