Okay this... was annoying, but how we were handling targets had some dumb issues:
we weren't including the config file in serialization, which means that we didn't have enough info to generate the repro command for gftools
(and also it was possible to end up with distinct targets serializing identically, in the case where a repo contained multiple configs which pointed to overlapping sources; not sure if this existed but was possible)
but I also want to be efficient in what we serialize, and the config and source paths generally share a stem
because we serialize to json and use targets as the keys, we need to ensure they serialize as strings
so the logic got complicated fairly quickly.
I have the repro command fix working on top of this, and will PR that separately.
Okay this... was annoying, but how we were handling targets had some dumb issues:
I have the repro command fix working on top of this, and will PR that separately.