This is genuienly one of the best error messages I've ever seen. What makes it so great?

1. Starts with a clear, non-technical description of the problem.

2. Follows that with a clear _technical_ description of the problem.

3. Suggests a solution to the problem and offers to automatically implement it

4. When that fails, provides another clear technical explanation (no non-technical one this time; that's fine because we're now into issues only triggered in advanced use cases)

Fantastic!