@brad.king This is another instance of this regression. See this issue as well. The latest 3.18 should have this fixed.