Extensions don't seem to get constraints that are not `==`
Open
Nobody has claimed this yet.
bug
extensions
- Dominant language
- C++
- Stars
- 23.6k
- Forks
- 2.6k
- Avg merge
- 6d 7h
- Merged PRs (30d)
- 14
Description
I'm not sure if this is expected or not, but it appears that extensions do not get the constraints for operators that are not ==. I see this on both osquery-go, and osquery-python. In both the current 4.5.1, and 3.3.2.
I've tested this using some simple pp dump statements in test extensions.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by reproducing the behavior with the mentioned pp dump statements in test extensions for osquery-go and osquery-python, comparing == with other operators; done means the constraint behavior is understood and the issue is fixed or confirmed as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, go, python, sql
- Domain
- api, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100