Jose Blanquicet

Notice we are also missing a section on the README for the local-gadget.

Some other suggestions here: https://github.com/kinvolk/inspektor-gadget/pull/1014#discussion_r988718265. > Notice we are also missing a section on the README for the local-gadget. > Done in https://github.com/kinvolk/inspektor-gadget/pull/1006

For top gadgets, we already know in advance the number of rows/entries we will print (the `max-rows` value), so I was wondering if we could use a `tabwriter` as we...

Notice this issue is only focused on refactoring code on each category so that we can **then** (in [#638](https://github.com/kinvolk/inspektor-gadget/issues/638)) move the refactorized code to a common package and use it...

Reopening this issue as discussed [here](https://github.com/kinvolk/inspektor-gadget/pull/782#issuecomment-1222359717). The top category needs to be refactorized: - [x] https://github.com/kinvolk/inspektor-gadget/issues/849

Thanks @eiffel-fl for sharing this. Yeah, 2 would be OK. Thanks!

What do you suggest using? For instance here: ```golang t, err := tracer.NewTracer(config, enricher, eventCallback) if err != nil { return nil, fmt.Errorf("creating tracer: %w", err) } ``` We should...

> I don't think it's worth switching to the pull approach, as you would run into the same issue when there's more than one node. At one point you have...

Thanks @invidian! The issue is that the documentation does not follow the current implementation. I noticed multiple misalignments: - As you said, the biolatency gadget is not currently supported by...

> Should I open a separate issue then if I would like `biolatency` to be available as a local gadget? Thanks @invidian! It created a more general one (https://github.com/kinvolk/inspektor-gadget/issues/720) given...