Just subscribing to this thread as I've noticed this error as well, though it's not affecting deployment in my case.