This issues is now fixed in 1.5.0
Update: The duplicate comment has been removed from the main thread, but feel free to follow up here.
