Melissa Kilby comments

Results 548 comments of


                                            Melissa Kilby

feat(libsinsp/container_info): change default / init lookup state to `FAILED`

Unit tests just needed to be updated w/ `set_lookup_status(sinsp_container_lookup::state::SUCCESSFUL)`.

feat(libsinsp/container_info): change default / init lookup state to `FAILED`

Exactly @leogr there was never a milestone since it's not particularly urgent from a functionality point of view, but it's one step towards making sure we don't break the container...

feat(libsinsp/container_info): change default / init lookup state to `FAILED`

Rebased so that the new container e2e tests can run.

feat(libsinsp/container_info): change default / init lookup state to `FAILED`

Updates on this PR? Thanks.

Add `Package.resolved` and `dependabot.yml`

> I don't think that we should go ahead with this PR. The recommendation right now is to not commit the resolved file in libraries since the file has no...

Add `Package.resolved` and `dependabot.yml`

> Yeah, it is not useful to have a Package.resolved in libraries. > > Package.resolved isn't a real lock file; it doesn't matter at all in libraries either since consumer...

fix(build): metrics compilation after refactoring into classes

@Molter73 we usually have the habit to bump both libs and driver during the dev phase. Few times we didn't do it and it caused compatibility issues. If you agree...

fix(build): metrics compilation after refactoring into classes

/hold for possible patches https://github.com/falcosecurity/falco/issues/3271#issuecomment-2206918760. Do not merge prior to having made a decision.

new(config): add `container_engines` config to falco.yaml

/milestone 0.39.0

new(config): add `container_engines` config to falco.yaml

Re unit tests: Curious to know where to add tests as for most configs we do not have any here except for example for `engine_modern_config.yaml` etc. And / or likely...