That’s one of the reasons I’ve been slowly patching out the query calls happening on the config fuzzer side. I know I likely have to patch away the ATC ones now

Hey small heads up, the CI is often failing because macOS Catalina jobs are getting canceled due to a scheduled brownout. I’ve opened a PR since I’ve noticed this: https://github.com/osquery/osquery/pull/7700, would need a review. I’ve also opened an issue for tracking updating the build to Monterey: https://github.com/osquery/osquery/issues/7702

Hey friends, who handles payments for the osquery slack these days? I realized that I'm the only one listed as a billing contact, curious who else would like to be on the list for billing stuff? Lemme know!

I’m an owner on the account. (As are various other TSC sorts). AFAIK facebook is still paying for it without asking too many questions, so that’s probably why you’re the billing contact

Mmk.. Do we have a list of emails for the TSC members somewhere? I'll just add everyone >.>

If we're going to keep this on the 5.5 milestone, someone with a fleet should test it (distributed queries) https://github.com/osquery/osquery/pull/7675

There's a couple of feedback comments from @seph on this PR he approved — if these aren't actionable requests, or if he wants to resolve them, I will just merge this https://github.com/osquery/osquery/pull/7502

I think 7502 is the only thing on the 5.5 list that looks quickly meergable

Shall we try to get https://github.com/osquery/osquery/pull/7721 (bugfix for battery table on M1) into this release? I can test on another couple of systems.

i’m good either way. I kicked CI

Hey y'all, what else is needed to cut the 5.5 prerelease?

https://github.com/osquery/osquery/milestone/63 This one seems trivial enough, shouldn't be blocked as much as it is https://github.com/osquery/osquery/pull/7621

I'm moving issue 7104 to the next milestone, it's just a reminder and shouldn't block the release

Other than that, Stefano is updating the

libxml2

package dependency

Look for the requested change on PR 7710 to be addressed this afternoon

https://github.com/osquery/osquery/releases/tag/5.5.0 is up

I just cut https://github.com/osquery/osquery/releases/tag/5.5.1 This includes a sqlite update. We do not believe osquery to be effected, but like ever, people like to know we’re on top of these.

Updated the codesign repo to a new ubuntu. https://github.com/osquery/osquery-codesign/pull/40 @Stefano Bonicatti Want to glance at then when you have a moment

Do we have a flaky windows integration test? I've re-run this CI twice on @seph’s Markdown-only change https://github.com/osquery/osquery/runs/7923758410?check_suite_focus=true

probably…. I did just merge https://github.com/osquery/osquery/pull/7742

close and reopen the changelog?

Yeah it wasn’t flaky, it was always failing; 7742 should fix it

5.5.0 Change log is ready to approve / merge https://github.com/osquery/osquery/pull/7737

I mean 5.5.1

I think you can reasonably approve that

not I, but maybe @Stefano Bonicatti can when he returns

Fleet has been running osquery 5.5.0 for ~a week internally now and our automated tests also seem to be working.

A user has opened a couple of issues about the documentation of

hidden

columns in tables. https://github.com/osquery/osquery/issues/7750 Are they intended to be documented? They're hidden by default, not because they are secret or intended not to be used, right?

Anything we can do today to move 5.5.1 to official release?

Oops I forgot before I left town. Let me see if I can do this from my phone.