I'm still seeing this happening with 2.0 release code ...