I see the same error on one of my test servers running master. I suspect it's related to one of the visibility fixes that made it into 3.0.3.
I see the same error on one of my test servers running master. I suspect it's related to one of the visibility fixes that made it into 3.0.3.