Leonardo Grasso

Badges for "dev" package are not reporting the correct version

10

**Describe the bug** As per the title. **How to reproduce it** Look at the [README.md](https://github.com/falcosecurity/falco#latest-releases) :point_down:  **Expected behaviour** Badges should report the latest version on the...

Remove Mesos support

8

**What type of PR is this?** /kind cleanup **Any specific area of the project related to this PR?** /area engine **What this PR does / why we need it**: Mesos...

CI issue: data race in publishing jobs for `-dev` packages

5

**Describe the bug** When multiple PRs got merged at the same time, then the CircleCI may run multiple workflows in parallel. In such a situation, a data race occurs while...

"BPF doesn't have JIT enabled" reported incorrectly when using docker

34

**Describe the bug** Even if JIT is enabled for BPF, both `falcosecurity/falco` and `facosecurity/falco-driver-loader` are reporting the following message when run with `-e FALCO_BPF_PROBE=""`: ``` ****************************************************************** ** BPF doesn't have...

[UMBRELLA] Dropped events

33

## Why this issue? When Falco is running, a producer (a.k.a the [driver](https://falco.org/docs/event-sources/drivers/)) continuously forwards events to a consumer (the Falco userspace program) with a buffer that sits in the...

build: syncing the repo metadata even when an RPM or DEB package is deleted afterword

29

**Motivation** When releasing a new version, a new git tag triggers the CI to build and publish packages. During the RPM and DEB publishing process, the new package is uploaded...

The outputs throttling mechanism skips notifications without any notice

13

**Motivation** The current throttling mechanism can be configured within [falco.yaml](https://github.com/falcosecurity/falco/blob/master/falco.yaml) as shown below: ```yaml # A throttling mechanism implemented as a token bucket limits the # rate of falco notifications....

Improve rule files validity checking

49

**Motivation** Currently, if some properties are misplaced within the rule's document (ie. the YAML file), no warning is emitted and non-obvious side effects can occur ([here](https://github.com/falcosecurity/falco/pull/1273#issuecomment-662406908) an example regarding `required_engine_version`...

Make clear that git notarization ignores untracked files and changes not staged

1

`vcn n git://...` is actually notarizing just the commit which HEAD is pointing to. If there're untracked files or changes not staged, then both notarization and authentication will ignore them....

modpost failing message for bpf

4

**Describe the bug** When building the bpf probe, I get the following `make` errors :point_down: ``` ./include/linux/fortify-string.h:92:17: warning: passing 'unsigned char *' to parameter of type 'const char *' converts...