Bryan Boreham

@azaars I believe this is fixed in https://github.com/weaveworks/weave/pull/2950 Not sure how long that will take to propagate to the Store.

OK, I don't think that was the same problem, but I just tried it myself and seems ok: ``` root@bryan-dev2:~# docker plugin install weaveworks/net-plugin:latest Plugin "weaveworks/net-plugin:latest" is requesting the following...

What I had in mind would change `Caller` and add `Helper`, plus there needs to be somewhere on the logger data structure to hold the set of helpers. I can’t...

One real case is https://github.com/grafana/dskit/blob/9956e2453a9fc2e88246578adafee7c6d7de176a/spanlogger/spanlogger.go#L80 where we want to send the same log message to tracing and to a go-kit logger; we have a lot of `caller=spanlogger.go:80` in our logs....

Exactly.

How would I know `4` is the correct number, in general?

I don't think that is realistic in a large program made up of many packages.

> Almost like it produces the json in memory and then produces the yaml. This is correct - in Kubernetes yaml is produced by translation from json. Ironic, for a...

FYI @brb has found some kernel race conditions which relate to this symptom. See https://www.weave.works/blog/racy-conntrack-and-dns-lookup-timeouts for technical details

@vincepri presume you meant OpenTelemetry. I opened a PR to make it easier to see what I've done: #1211