Incorrect line in error response for Undefined Type when followed by '!' (non-nullable)

Looks like a bug which is probably coming from the underlying library that we use. I have marked this as accepted and we’ll get to it next month.