Any chance this can be ported to 5.0 branch? The problem still exists in release 5.0.2, even though it was reported 5.0.0-rc2.
Any chance this can be ported to 5.0 branch? The problem still exists in release 5.0.2, even though it was reported 5.0.0-rc2.