Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Constraints that are not == don't appear to be passed along #88

Open
directionless opened this issue Oct 28, 2020 · 1 comment
Open

Constraints that are not == don't appear to be passed along #88

directionless opened this issue Oct 28, 2020 · 1 comment

Comments

@directionless
Copy link
Member

As pointed out on slack, it's not clear how to get a constraint that isn't ==

I added a spew to table.Call and I don't see the constraints coming in.

If I look at a trace in panic, I don't see much in between that, and the thrift layer.
@directionless
Copy link
Member Author

directionless commented Oct 28, 2020 •
edited
Loading

This issue appears present in both the python sdk, and the go one. And in both osquery 4.5.1 and 3.3.2. Upstream it is!
osquery/osquery#6734

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@directionless