Zhiqiang ZHOU

> > Signed-off-by: STRRL > > Thanks, but please use real name Updated!

Hi @AkihiroSuda @junnplus , I meet some trouble when using `TabReader` to parse the output of `buildctl prune`. The output of the `buildctl prune` is not soo standard, it would...

What should I do now? Make a new implementation like `TabReader` but only for `buildctl prune`? or wait https://github.com/moby/buildkit/pull/2992 getting merged?

> What should I do now? Make a new implementation like `TabReader` but only for `buildctl prune`? or wait [moby/buildkit#2992](https://github.com/moby/buildkit/pull/2992) getting merged? I just noticed that PR already get merged!...

> I think I could update code based on the json output! > > > Are we not compatible with older versions? Well, if we want to be compatible with...

> > The output of the buildctl prune is not soo standard, it would use both \t and white-space as the delimiter: > > You can convert `\t` to whitespace....

> > What about using BuildKit Go API? I prefer to use that instead of parsing the text, because go API seems more stable and easy to use. thinking >...

It has been a long time since this PR not active, I would continue the work in another PR with new codebase.

Hi! I want to take it a try! Could you assign this issue to me? :heart:

Hi! I am interested in this issue; And there are some related changes on upstream go-logr/logr, logr introduces [`logr.Marshaler`](https://github.com/go-logr/logr/blob/master/logr.go#L498), which seems aims to resolve this situation, as the description in...