This is already fixed internally and will be in the upcoming 4.1.x beta release, thanks for reporting.