Brendon Go

@zakrush we are unable to reproduce this error. Building on an ubuntu or MacOS machine works without issue. Maybe there is something going on with docker in Archlinux or how...

Looks like there was a problem running threads with asyncio. Similar issue without fix: https://github.com/KimiNewt/pyshark/issues/353 Not entirely sure what is happening since it looks like you are running python 3.7....

@toastyghost @sumitsharma16 are you able to provide reproduction of the issue? Trying out on a few repos we are unable to get this error.

@spmishra121 this looks like a different error. You seem to be running a stale version of semgrep. If you upgrade to latest and run again it should work

@sumitsharma16 @toastyghost @ajinabraham closing this as unable to reproduce. Feel free to reopen an issue with a reproduction if this is still happening

The proposed changes sound good btw.

The document in brakeman we link to is actually under MIT license: https://github.com/presidentbeef/brakeman/blob/v3.6.2/MIT-LICENSE https://github.com/presidentbeef/brakeman/blob/v3.6.2/docs/warning_types/ssl_verification_bypass/index.markdown so for this specific case there is likely no issue. We'll update the pointer. In general,...

Hello @abhinavbansal19961996 ! Generic is your best bet for now. We're currently focusing on the performance of semgrep on the GA languages. We can track interest in gradle support using...

Hi, @rakeshmane would you mind adding an entry into the changelog for this (e.g. https://github.com/returntocorp/semgrep/blob/develop/changelog.d/pa-3014.fixed)

semgrep pulls from registry to pull the extra validation rules https://github.com/returntocorp/semgrep/blob/develop/semgrep/semgrep/core_runner.py#L454