raulk

Yeah, I've encountered this hindrance in the past. I get the impression the goal was to enable diversity of multiaddr implementations, but I can't see a use case for that.

Ah, I see what you mean. Treating `Multiaddrs` as a canonical format with conversions from/to other formats. Unlike Rust, I don't think this is feasible in Go by making TCPAddr...

@hsanjuan I'm convinced. Multiaddrs are used everywhere, this indirection has proven useless over time (we have zero alternative implementations), adds a performance cost, and multiaddrs are a _data containers_ per...

@lthibault Sorry to hear that this caused a little bit of pain. One thing you can do is disable the GOPROXY entirely. We need to document this in https://docs.testground.ai, but...

Motivation: we can reliably reset the `docker:go` builder and have it remove all its dependent things instead of having to do a `docker system prune -a`, which also nukes other...

This is going to be tricky to achieve at build time, unless we inspect the dependencies of the test plan. And doing so would be language-dependent. We could introduce a...

When we introduce breaking changes in the Testground SDK interface, we bump up this magic number on both ends. If at runtime there's a mismatch, it'll be clear what's going...

Hey! I'm no longer maintaining this repo (I no longer work at ConsenSys). Maybe someone from the PegaSys team there could help? cc @rojotek @mbaxter @ajsutton

@gsalgado – great! If you need help, just post here :-)

@gsalgado took a first look and posted a few comments. Thanks!