Closed caglarsayin closed 2 years ago
Hi @caglarsayin sorry for the delayed response. We just released a new version of the agent last week that came with a bunch of file targeting fixes and I suspect this error you were seeing might have been caused by a binary file being treated as a go file? If you run the latest semgrep-agent
or even semgrep
it should complete without issue. Let us know if that is not the case .
No it is not a binary file but a go file that includes emojis because go accepts this kind of chars in the code
Ah I see. Moving this issue to semgrep repo
Actually my bad should not have done that and should have opened a separate issue. Moving back sorry for the noise
@caglarsayin since last week we have updated the invocation to not need the --debug option so semgrep-agent should be able to successfully complete.
Closing as done I think this works with semgrep 0.85.0 onwards
Thanks your are the best
I am scanning a go project which has utf-8 characters and semgrep agent is falling as in the example below
semgrep-agent --config p/security-audit --config p/secrets --baseline-ref master --json
I went deeper in the issue and and run the semgrep as shown above and here is the output.
The root cause of this issue a utf-8 character in a GoLang source code but it is quite usual fo go source code. As I understand since we use --debug option on semgrep, it is on --strict mode and it does not tolerate any issues.
Can we implement a work around?
Thanks