Problem with binary file
- Dominant language
- Python
- Stars
- 319
- Forks
- 55
- PR merge metrics
- No merged PRs in 30d
Description
When trying to analyze a private repo, using `git deps HEAD -e HEAD~2`, a pipe gets broken by an unexpected 0xa3 character (apparently £ in latin1 decoding).
git grep-ing finds that character only in a .png file we have in the repo, so my guess is a problem with parsing `git blame` on binary files.
However, this only happens when using -e, so I am not sure that this description is accurate. I am short on time, so I can't look for a better reproducer, but after new years if I can try to get one if you need
Contributor guide
Research direction
Start by reproducing `git deps HEAD -e HEAD~2` against a private repository containing the reported .png file, then trace how `-e` processes `git blame` output and binary files. Check where the 0xa3 character reaches the pipe and confirm that analysis completes without breaking on binary content.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100