Skip to content

Conversation

@zwass
Copy link
Member

@zwass zwass commented Dec 24, 2024

I think it is easier to understand the results when the values that are not relevant are set to empty/null rather than explicitly set to zero. I think that explicitly setting to zero might be a leftover from the time when osquery couldn't handle empty column values.

I think it is easier to understand the results when the values that we don't know are set to empty/null rather than explicitly set to zero. I think that explicitly setting to zero might be a leftover from the time when osquery couldn't handle empty column values.
@zwass zwass added virtual tables macOS Linux events Related to osquery's evented tables or eventing subsystem labels Dec 24, 2024
@zwass zwass requested review from a team as code owners December 24, 2024 18:55
Copy link
Member

@directionless directionless left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My understanding is that there are still places we panic if there are NULL columns. But probably not here!

@directionless directionless merged commit b30bb81 into osquery:master Dec 28, 2024
22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

events Related to osquery's evented tables or eventing subsystem Linux macOS virtual tables

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants