This will anyways be unnecessary after 1.24, and given that it's possible to copy over the file, I'd prefer to avoid bundling the file with the tool. Let's just use the 2 locations to check for the...
I'm wondering if this problem still exists with the latest codebase and Go versions? I suspect it may be a runtime issue.
Is there a command that will allow me to reproduce this error immediately?