Go R1 Day 61
It was a dark and stormy night. The world was bleak. A command was sent to The Compiler.
The assumptions were flawed. The command was rejected.
You have given me an invalid command with
-argument-that-shall-not-work 5being invalid.
But I’ve provided
--argument-that-shall-not-work, the indomitable wizard said.
Your command is unworthy.
Digging into esoteric tomes of knowledge, the wizard discovered others have had similar issues when calling external processes using the legendary wizardry of
However, none could shine light into the darkness of his failure.
pwsh worked fine.
Next, the wizard tried a variety of escaping commands.
- Using back-ticks with the arguments to escape.
- Using partially quoted arguments in the slice of the strings.
- Using no quotes.
- Went down the path of ancient texts describing similar issues.1
To the wizards dismay, copying the printed debug output worked fine in the terminal, but alas would not be executed by The Compiler.
It began to feel like the curse of dynamic SQL queries that had long plagued the wizard until PowerShell had been discovered.
The wizard ruminated on his plight. He thought:
At the end of the day, all things seem to come down to strings and the cursed interpretation of my textual commands to The Compiler. How many a day have I wasteth upon the fault of a single character. The root of all evil must be a string."
The wizard connected to a new remote instance, using the power of the Remote SSH plugin and began debugging in VSCode.
The debug breakpoint config that worked was set in stone.
Consulting The Sage (aka Debugger), it advised the wizard of the message sent to The Compiler.
The wizard had a revelation. A fellow wizard advised to break the appending into individual statements instead of trying to do so much in one step.
The incantation changed from:
to the following:
The foe vanquished, the The Blight of Strings was cast aside with malice. The wizard swore to never fall prey to this again.
Josesh[^similar-issues] pointed towards: EscapeArgs. I did not find any equivalent for Darwin. The closest thing I could find was execveDarwin which I believe is the execution line, which gets the argument list from: SlicePtrFromStrings which is defined at here
I’ll have to re-examine in the future when I have more experience with Go, as it’s not a simple chain to follow.
This pointed towards a similar issue with the
\n showing up.
The Compiler’s heartless gaze felt nothing. In the shadows, The String Balrock bid its time, knowing that the wizard would suffer once again.