There was a report of this a few weeks ago, which has now been fixed:
Though if you’re on 3.2 tracking the stable
branch you may need to wait for the next release to pick that fix up.
There was a report of this a few weeks ago, which has now been fixed:
Though if you’re on 3.2 tracking the stable
branch you may need to wait for the next release to pick that fix up.