I'm looking at a build that's about to hit an hour on this step and fail and honestly it's just....SO EXCITING! BECAUSE I ADDED LOGGING TO FIGURE OUT WHAT THE FUCK IS WRONG! WOOOOOOOOO! Can't wait, highlight of my day.
Fuck. That didn’t work.

OMFG, it's happening because I made builds faster. This nightmare to debug (because it happens in a remote secure container) is evidently a combination of:
1. A unit test result folder that slipped into the file set
2. A test output folder being time-based but only down to the millisecond, so think: <Prefix>_12_01_02.123\
3. When there's a collision (e.g. 2 at the same millisecond), there's an indexer, making it <Prefix>_12_01_02.123[2]\
4. The PowerShell script wrapping some other functionality in a package wasn't using -LiteralPath with user-input file paths, which means it thinks that `[2]` is a Regex.

My brain hurts.

@Nick_Craver wow, one of those, huh
@KirillOsenkov I mean official builds are still hella long so been accomplishing other things during runs but...yeah, basically spent a week figuring this freaking thing out

@Nick_Craver this is hilarious, relatable, depressing, predictable, and arguably better than parsing html with regex.

Thanks for the smiles.

@Nick_Craver sounds like a con talk! “Weird Crap I’ve Had To Deal With”
@Nick_Craver I love reading the minutia of the things you are working on 🤗. Sometimes they hurt my head as well 😂. Seems like you are at least enjoying your new work 😘🙌.
@Nick_Craver congrats on tracking it down! i've hit a version of 3 before in a web app (it only showed up on apple silicon macs!),, and that alone was almost enough to break me.
@Nick_Craver Everything was OK until I hit the PowerShell regex part...
@malwareminigun Jealous, aren't ya?!?
@Nick_Craver No, because there is PowerShell in vcpkg too and now I'm wondering how screwed we are