You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Windows 10, WSL
PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
Additional Context
PR #2174 replaced go-git with direct calls to Git. While this fixed memory consumption issues, it seems that more work is required to stabilize the change.
References
N/A
The text was updated successfully, but these errors were encountered:
I have a new GitHub repo which is failing 100% with "error":"signal: broken pipe" when reading a .tar file which I believe is being broken into several files. This seems similar to this issue #2419
It sure does. @dwilliamsstc would that repo happen to be public, so that we can use it to test against? I thinkthis PR should address the issue, but i'm not 100% certain just yet.
@ahrav The issue isn't specific to any repo or file — as far as I can tell. For me, some scans encounter no issues, whereas other scans have the issue on ever file.
Please review the Community Note before submitting
TruffleHog Version
3.67.5
Trace Output
This often seems to be preceded by archive errors, but not always. I'm not sure what to make of that, as I haven't looked into the code path yet.
Expected Behavior
Binary files are reliably read from Git repos.
Actual Behavior
Reading binary files from Git repos intermittently fails due to a
signal: broken pipe
when executinggit cat-file
.trufflehog/pkg/sources/git/git.go
Lines 1168 to 1193 in f35185e
Steps to Reproduce
Unsure; it does not consistently happen.
Environment
Windows 10, WSL
PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
Additional Context
PR #2174 replaced go-git with direct calls to Git. While this fixed memory consumption issues, it seems that more work is required to stabilize the change.
References
N/A
The text was updated successfully, but these errors were encountered: