Adam

@dsnet I understand. I've opened the following issue over here: https://github.com/protocolbuffers/protobuf/issues/11505

Too bad, but thank you for the quick response.

Cool! these are some interesting thoughts. I'm not that deep into the codebase but: 1. For me that would not be confusing, I've been learned to isolate each node pretty...

I would still like to see this, I ran into this again today. For now I only needed it for string keys so I've created this: ```Go // foreachKeySorted iterates...

I would love to see a rule that forces consistent use of explicit message id or no explicit message ids. If developers mix one or the other it should be...

Thank you for issuing this request! We've put it on the upcoming milestone and will start with a design for this feature.

As a first step we should provide feedback on what happening (e.g opening browser window, waiting for redirect), as a second step we want to provide solid option for when...

I agree that removing the reference is probably confusing, if we decide to fetch the pods as part of the dataset listing (to see if the referenced job still exists)...

Alternatively, maybe the flex volume error is available as part of the pod status that we're already fetching for the list overview. Using that would be lot less work but...

Having talked with @Overv this is more difficult than anticipated for several reasons: 1) The Pod information we're already fetching does not contain any flex volume errors. 2) The Kubernetes...