Thanks for these two fixes.
We're actually planning on pulling in 1.13 fairly soon; it's already staged in our git tree. I've verified these two patches are already included in our tree (git commits 32603f57 and 855003c3), so that should sufficiently address this bug.
Thanks for these two fixes.
We're actually planning on pulling in 1.13 fairly soon; it's already staged in our git tree. I've verified these two patches are already included in our tree (git commits 32603f57 and 855003c3), so that should sufficiently address this bug.