We were bitten by this last week on 2.2.19, rolling in the patch fixed the issue.
Big +1 to get this fixed upstream.
We were bitten by this last week on 2.2.19, rolling in the patch fixed the issue.
Big +1 to get this fixed upstream.