Thanks, I have updated the blog post accordingly. There is a conspicuous note at the top now saying the problem will be fixed in version 38. I think the blog post still makes sense, as it will be a while for the fix to become effective for everybody.
