The commit for this issue came in through 3.0.22 upstream stable update, so we can mark this as verified.
The commit for this issue came in through 3.0.22 upstream stable update, so we can mark this as verified.