Juliana Fajardini Reichow

Replaced by: https://github.com/OISF/suricata/pull/7723

> I wonder if this actually works with our CI check. I _think_ that checks each commit. Looking at https://github.com/OISF/suricata/blob/master/.github/workflows/formatting.yml#L139, I think that it checks each commit, but won't print...

> Hello. Is there any documentation to help build and run suricata+dpdk. Thanks. Hi! There's this, from our userguide: https://suricata.readthedocs.io/en/latest/configuration/suricata-yaml.html?highlight=dpdk#data-plane-development-kit-dpdk And there's also a presentation from last year's SuriCon, which...

The CI Fuzz failure here seems to be the same that already exists in master-6.0.x, due to pcre-1 usage...

> A few questions: > > 1. Is there a way to check the output of the output of the formatting script? Is this related to clang? If so, you...

> > Hello! I just approved the CI checks again, but I believe that for those changes you should also be able to check the CI tests in your forked...

> @jufajardini Definitely. Thanks for the advice! Any idea why the build scripts aren't running on my machine? > > ``` > ➜ suricata git:(whitespace-bug) ./scripts/clang-format.sh whitespace-bug > ./scripts/clang-format.sh: command...

> > No need to replace `branch` with your branch-name there. Would that help? > > Same issue actually thinking Talkin about versions... what's your clang version? I see that...

> > > > No need to replace `branch` with your branch-name there. Would that help? > > > > Same issue actually thinking > > > > > >...

> @victorjulien @jufajardini Looks like the 2 "fuzzer" checks are failing, but everything else is passing. It's giving me the following error: > > ``` > + cd .. >...