Based on that issue, and the corresponding commit that resolved the problem, the fix does not exist in 2.0.0.2. It was first introduced for the 2.1 release.
Is there any chance that the comment can be updated then to reflect that it didn’t actually make it into 2.0? If I had known it was actually in 2.1 I would have upgraded sooner