Gabriel Hartmann

@yugangw-msft Are you sure that pull request addresses the error message situation? Is the cli now producing error messages of the type: "Unexpected non-string token: [nicName] on line 42." ?

@vivsriaus: Thanks for addressing this. I haven't used the azure cli since shortly after this bug was filed (a year ago), and no longer use it at all, so I...

@mohitsoni: Why is this change needed? Is this needed at all anymore, now that the suppress/revive work has landed?

@mohitsoni: The needed change in binary dependency has been made. All tests have passed. Can you get this PR across the line if it is still needed?

For terminal status, retry should continue until deletion grace period expires. For non-terminal status, the virtual kubelet should be continuously reconciling state with the API server and never giving up...

Those both sound like good ideas to me, that don't preclude further improvements to the reconciliation logic in more challenging failure recovery scenarios.

In effect this behavior is implementing a `restartPolicy` of `Always` for lost status updates.

@cpuguy83 : Step 3 was in my case `docker kill `

@edenhill Why is this issue closed? I'm seeing the same thing as everyone else, also calling `ReadMessage` quickly in an infinite loop. I personally see this issue associated with a...

@ftrossbach: Other merged PRs have moved 0.6.2. Is this PR still relevant?