Hi @ilpianista the CI fails the code style check, but you can run the step explained here and push a new commit to make it pass: https://osquery.readthedocs.io/en/latest/development/building/#formatting-the-code

I agree the two directories you mention should not be searched as if they were Profiles. Do you know if those names are always the same across platforms and language localizations?

Hi @ilpianista the CI fails the code style check, but you can run the step explained here and push a new commit to make it pass: https://osquery.readthedocs.io/en/latest/development/building/#formatting-the-code

Thanks, fixed!

I agree the two directories you mention should not be searched as if they were Profiles. Do you know if those names are always the same across platforms and language localizations?

I'm not 100% sure, but I found the Italian documentation page about crash reports and it mention the ~/.mozilla/firefox/Crash Reports/ folder, so, apparently, no translation is performed.

I think the CI failure is real:

/__w/osquery/osquery/workspace/padding-required-by-rpm-packages/src/osquery/tables/applications/browser_firefox.cpp:202:48: error: no member named 'ends_with' in 'std::__1::basic_string<char>'
                                      return s.ends_with("Crash Reports") ||