search

gitleaks / gitleaks-action

Protect your secrets using Gitleaks-Action
https://gitleaks.io
Other
319 stars 122 forks source link

Error During CI #135

Closed chandanpg closed 7 months ago

chandanpg commented 7 months ago

Since today, we are getting below error for our NextJS Repo. Earlier it was working fine but now seeing this issue.

please note that we are using gitleaks/gitleaks-action@v2 Actions to call Git-Leaks

SyntaxError: Unexpected token < in JSON at position 0 at JSON.parse () at IncomingMessage. (/home/runner/work/_actions/gitleaks/gitleaks-action/v2/dist/index.js:70890:22) at IncomingMessage.emit (node:events:525:35) at endReadableNT (node:internal/streams/readable:1358:12) at processTicksAndRejections (node:internal/process/task_queues:83:21)

lucaspierru-convelio commented 7 months ago

Same issue for us this morning, most likely a licensing server issue :thinking: 

[x] is an organization. License key is required.
undefined:1
<!DOCTYPE html>
^

SyntaxError: Unexpected token < in JSON at position 0
    at JSON.parse (<anonymous>)
    at IncomingMessage.<anonymous> (/home/runner/work/_actions/gitleaks/gitleaks-action/v2/dist/index.js:[7](https://github.com/x/salesforce/actions/runs/x#step:3:8)0[8](https://github.com/x/salesforce/actions/runs/x/job/x#step:3:9)[9](https://github.com/x/salesforce/actions/runs/x/job/x#step:3:10)0:22)
    at IncomingMessage.emit (node:events:525:35)
    at endReadableNT (node:internal/streams/readable:1358:[12](https://github.com/x/salesforce/actions/runs/x/job/x#step:3:13))
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
Tonomis commented 7 months ago

Same here (same logs)

frastefanini commented 7 months ago

Same here. Seems like keygen.sh is down right now, directly impacting this action: https://status.keygen.sh/

chandanpg commented 7 months ago

Looks like it has started working now. Does anyone know if anything was done to fix this ?

zricethezav commented 7 months ago

Same here. Seems like keygen.sh is down right now, directly impacting this action: https://status.keygen.sh/

Should be resolved now. Sorry for the inconvenience

vs-vi commented 7 months ago

Again it has been started.

darkcyber1337 commented 7 months ago

again, same error here.