Yep, got bit by this exact behavior too, returning a typed nil error as the error interface. The check for err == nil said false, although we were returning a n

Yep, got bit by this exact behavior too, returning a typed nil error as the error interface. The check for err == nil said false, although we were returning a nil typed error...