Trouble with (some) unix epoch timestamps
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 10.6k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
We fail to parse commits with committer/author times that are set to the unix epoch in some cases. https://github.com/libgit2/pygit2/issues/947
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests; start by reading and reproducing the failure described for commits whose author or committer time is the Unix epoch, using pygit2 issue 947 for context. Trace the relevant libgit2 commit-time parsing path and verify that affected commits parse successfully without regressing other timestamps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, git
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100