Peter Ebden

Hmmmm right so it has picked up `amd64` from somewhere; that _should_ be coming from `runtime.GOARCH`, although it's a bit indirect. Can you confirm whether this is actually the `darwin_arm64`...

I agree, adding it at the top level produces ugly import paths with `v2` repeated (or even worse, `v2/.../v1` in the case of the Asset API), which seems like a...

I've had a play with my suggestion above. I still think theoretically it should be able to work but in practice still seemed to get hung up about the repo...

Thanks for looping us in on this! Please's [Go plugin](https://github.com/please-build/go-rules) has most of the module information available to it; these days it's typically synced from the go.mod file using [Puku](https://github.com/please-build/puku)....

I don't think this is quite the issue - it should indeed issue each dependency once. The above example works if I create a BUILD file with just that in...

Okay I've moved this on a bit more; it's working a bit better now but still quite a bit of wonkiness. It feels like it's going to be hard to...

So we ran across this using more or less the same code as above (hence why I sent #188). From my perspective the current behaviour is undesirable; it silently converts...

Apologies for the delay - I haven't had any time to look into this further (and probably won't soon unfortunately). Thanks for picking it up!

Filegroups don't work very well in rex full stop. Ideally they would be done completely locally with zero RPCs; actually we create a synthetic AR and send it to the...

At present we don't have an explicit representation of the call stack available (it's recreated on the fly when errors occur). I can see where it'd be useful, but unsure...