Leo Antunes

hi @vtolstov ~Not sure I understand what you mean. Go 1.18 [still hasn't exported the underlying error](https://cs.opensource.google/go/go/+/refs/tags/go1.18:src/internal/poll/fd.go;l=18). (note the `internal` path)~ ~Or am I missing something? :thinking:~ (nevermind; see below)

Ah, I take it back: looks like it was indirectly [exported in 1.16](https://cs.opensource.google/go/go/+/refs/tags/go1.16:src/net/net.go;l=645). I'll see if that works.

Nice proposal! Just some drive-by-bikeshedding from a random user: Wouldn't naming the interface `Args` instead of `ArgSpec` fit better with the existing `Flag` interface? Maybe even `Arguments` or `ArgumentGroup`, since...

Now that 1.19 is out and 1.17 is EOL, can we reconsider this? :pray:

> Is there a particular use case beyond avoiding an AsSlice() call in your code? Not really. I just had a cursory look at the code and naively expected the...

Alternatively, grpcurl could follow up on #57 and add a `-recursive` option to describe, so that the whole accessible "tree" of services and types would be described in a protobuf...

@jhump ah yes, that makes sense. I'm coming from the "easy" case of single package proto definitions, so it would be enough for us, but not for a lot of...

Hi @devMls Back when I started coding this project, docker swarm had already kind of "lost the orchestration wars" to kubernetes. In the meantime its position has only gotten worse,...

hi @sighphyre! Totally understand the reluctance. I'll cook up a PR and check how much would actually break.

FYI: I'm also seeing the same behavior on 1.7.5 and I'm not using KV (using json on an EBS volume; single instance), so the issue label might be misleading for...