This issue is fixed in 3.1, but not 3.0. We could possibly backport it to the 3.0 series so it makes it into 3.0.3.
This issue is fixed in 3.1, but not 3.0. We could possibly backport it to the 3.0 series so it makes it into 3.0.3.