Mauro Ezequiel Moltrasio

I've been analyzing this issue and will try to describe and narrow down the problem as best as possible. The base problem behind this issue is that information about files...

After discussing it internally, we have decided that the proper solution to this issue would be to create separate DBs for managers to handle/mantain the status of agentless devices. The...

We've solved this issue in our fork by limiting the number of times `_ReadElem` can be called recursively and moving the buffers out of the stack as @lockedbyte suggested. You...

Hi @jasondellaluce! > Maybe the falco-e2e-tester image might be renamed into sinsp-e2e-tester? This is very useful for Falco but does test sinsp effectively I completely agree, naming has never been...

Thanks for taking the time going through the PR and testing it out @Stringy! > when building the e2e containers, the context sent to docker was huge (~4.2Gb) and took...

I've rebased the PR on a newer commit to make sure everything is still working. I've also addressed the comments made by @Stringy and opened the PR up for reviews.

Just a quick FYI, I will rebase and fix the conflict once I'm done going through a few problems I'm getting with the e2e tests

I've rebased on top of master, fixed the conflicts and also fix some minor details that were causing the tests themselves to fail with the latest changes, but nothing major.

Hey @LucaGuerra, thanks for the review! As you correctly stated, the whole idea behind running tests as a container is to not have to install python dependencies in the host,...

Yes, I wanted to split the work on adding the tests to the repo and adding them to CI, otherwise this PR could bloat a little too much