Dominic
Dominic
Very interested in this, I get the same error on all operations I attempted on my bucket
I'm also interested in contributing code to semgrep (which uses bento) but this telemetry thing just put a hard brake on my intentions. I'm willing to be a participating community...
I was referring to [this page](https://github.com/returntocorp/semgrep/blob/develop/docs/development.md) that makes it seem like a build requirement. Glad to hear about the new direction!
The proposed solution is fine, but alternatively the tree could be displayed as ```text - a/b/c/ - d - e - f ``` until there's actually something under the shallower...
- Add a "not equal" to all existing filters - Add a "matches"/"does not match" filter on body - Add a "matches"/"does not match" filter on headers
I'd have used "Not Like" and "Not Contains" today if it existed :)
I like the "allow users to update with a single click" option (with some sort of notification telling you the update is available). When you're working on a big project...
I can also reproduce this issue on Arch Linux. If anyone finds a workaround I'm listening. :)
`fog-core` version < 2.2.0 depends on a vulnerable version of `excon`. Updating to 2.2.0 would also solve this https://nvd.nist.gov/vuln/detail/CVE-2019-16779.
I found that the error is thrown from [here](https://github.com/NationalSecurityAgency/ghidra/blob/2108a5ed4c8a16eaa00cde7eebdbbf67fe472dec/Ghidra/Features/Decompiler/src/decompile/cpp/printlanguage.cc#L29) in Ghidra code but I'm still trying to figure out what it is exactly