luciofsl opened a new issue, #8434:
URL: https://github.com/apache/incubator-devlake/issues/8434

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   Hello,
   
   We have noticed an issue with the gitextractor plugin where some commits are 
being skipped, supposedly because there is no parent commit. However, we can 
see on GitHub that these commits do have parent commits.
   
   This results in missing commits in the _repo_commits_, _commits_, and 
_commit_parents_ tables, which are essential for refdiff to associate all PRs 
with our deployment events (we're using the webhook method), especially if the 
missing commit is the reference of our deployment event.
   
   The behavior we're observing is causing mislinked commits and ultimately 
messing up our LTC metrics.
   
   This issue was reproducible in multiple DevLake instances.
   
   **Logs:**
   ```
   2025-05-08 15:56:09 time="2025-05-08 14:56:09" level=info msg="[pipeline 
service] [pipeline #4] [task #24] [Clone Git Repo] skip commit 
fc5331abf6a85be3812a17843a6a5d95330ca7dc because it has no parent commit"
   2025-05-08 15:56:09 time="2025-05-08 14:56:09" level=info msg="[pipeline 
service] [pipeline #4] [task #24] [Clone Git Repo] skip commit 
a9c9ad96860358ef6a1f32798d2a8456cbfc854a because it has no parent commit"
   2025-05-08 15:56:09 time="2025-05-08 14:56:09" level=info msg="[pipeline 
service] [pipeline #4] [task #24] [Clone Git Repo] skip commit 
1415b0bfa73946aac039282040dfb7c2100d9a8a because it has no parent commit"
   2025-05-08 15:56:09 time="2025-05-08 14:56:09" level=info msg="[pipeline 
service] [pipeline #4] [task #24] [Clone Git Repo] skip commit 
961c42266124b29836ebb085b20af1ce2b61f6d3 because it has no parent commit"
   ```
   
   A similar issue has been reported 
[here](https://devlake-io.slack.com/archives/C03APJ20VM4/p1740649303464129).
   
   ### What do you expect to happen
   
   The gitextractor should extract all commits and ingest them into the 
necessary tables.
   
   ### How to reproduce
   
   1. Using v1.0.1@e061ef2
   2. Create a Project
   3. Add a data source
   4. Create a webhook
   5. Collect data from last 6 months
   6. Check the logs from the gitextractor plugin
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   v1.0.1@e061ef2
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@devlake.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to