The issue has been fixed to the 2.0.x branch.