4 ms·
Git commit message aside, the described debug session raises a lot of questions about the crappy tooling developers rely on. "ArgumentError: Invalid byte seque
by ryandrake 3y ago
Git commit message aside, the described debug session raises a lot of questions about the crappy tooling developers rely on.
"ArgumentError: Invalid byte sequence in US-ASCII" is a terrible, hard-to-action error message. What file? What line? What byte sequence? This "let's give the user another problem to solve" style of error messages is pervasive in our tools.
Also, why does the tool even require US-ASCII as input in the first place? Are we still living in 1995?
Also, if only ASCII characters are allowed, why does the code editing tooling allow non-breaking spaces in source code? Is there a good reason for having such a character in this file? This problem could have been avoided if the editor could have been smarter or highlighted the "bad" character better.
This developer lost an hour of his life because of a cascading chain of defective tools.