This bug will be fixed when upstream commit fd8ef11 is applied to upstream stable v3.2. I see that it has already been applied to upstream v3.0, v3.4, and v3.6.
I'll monitor stable-queue and update the bug when the fix lands in 3.2.
This bug will be fixed when upstream commit fd8ef11 is applied to upstream stable v3.2. I see that it has already been applied to upstream v3.0, v3.4, and v3.6.
I'll monitor stable-queue and update the bug when the fix lands in 3.2.