That bug is fixed in previous 5.0.0 version. That means it’s solved. After current upgrade of course.