Since we're now on 3.1, on the verge of 4.0, we're not supporting 2.x or prior versions actively. If anyone is experiencing this issue in current versions, please file a new issue with updated context and repro steps. Thank you for understanding :)
Originally posted by @rusackas in #20991
Comment From: rusackas
Closing this, as neither the title nor the description provide any context on a reported issue. The link points to an old/closed issue. If you can file the details here about what's happening (especially in the new 5.0.0 release) and how to reproduce it, we can reopen it.