so I actually told them that I was seeing it in 2018.2 originally. They seem to think it's a 2019.1 problem, but I tried emphasizing that it was occurring before some accounts were upgraded.

I've seen the issue only in 2019.1, NS said they fixed it yesterday, but problem still persists (for Lazy.js anyway)