[Bug][Gitlab Connection] GitLab data collection is incomplete #8857

Activity

1. albusshirazi

   added

   type/bugThis issue is a bugThis issue is a bug

   on Apr 27, 2026
2. albusshirazi

   changed the title [-][Bug][Module Name] GitLab data collection is incomplete[/-] [+][Bug][Gitlab Connection] GitLab data collection is incomplete[/+] on Apr 27, 2026
3. dosubot

   added

   component/config-uiThis issue or PR relates to config-uiThis issue or PR relates to config-ui

   priority/highThis issue is very importantThis issue is very important

   severity/p1This bug affects functionality or significantly affect uxThis bug affects functionality or significantly affect ux

   on Apr 27, 2026
4. dosubot commented on Apr 27, 2026

   

   dosubotBot

   on Apr 27, 2026 – with DosuBot

   More actions

   This is a known behavior that was discussed in detail in issue #8818 [1]. Here's a summary:

   Why commits are missing: In incremental (normal) collection mode, the gitextractor plugin performs a shallow git clone (git fetch --shallow-since=<timeAfter>). Commits whose parent commits fall outside the timeAfter window are intentionally skipped to avoid writing incorrect diff statistics. This causes boundary commits to be dropped entirely from repo_commits and commit_parents tables [1].

   Why Full Refresh works: With FullSync = true, DevLake performs a complete git clone --bare with no time boundary, so all commits are captured [1].

   How to trigger Full Refresh: You're right that there's no persistent UI option for this. The FullSync flag is a trigger-time override only, not a blueprint setting. Your options are:

   1. Trigger via API with an external cron job:

      POST /api/blueprints/{blueprintId}/trigger
      {"skipCollectors": false, "fullSync": true}
      

   2. Extend timeAfter generously — set it far enough in the past that parent commits of all relevant commits fall within the window.

   3. Periodically update timeAfter via the UI to keep the collection window wide enough.

   Additional note: There's also a separate bug (#8742) where the GitLab plugin fails to create repos entries in project_mapping when scope entities are empty, which independently breaks DORA metrics. This was fixed in PR #8743 [2] — worth checking if your version includes that fix.

   ⚠️ Also avoid setting timeAfter to null via the PATCH API — there's a bug (#8516) where it gets stored as 0001-01-01 instead [1].

   To reply, just mention @dosu.

   ---

   Share context across your team and agents. Try Dosu.

   
5. albusshirazi commented on Apr 27, 2026

   

   albusshirazi

   on Apr 27, 2026

   Author

   More actions

   OK, #8818 issue is a question , I'm reporting the same issue as a bug since I'm experiencing it too without any way to solve it by myself and it requires a fix in this product ability to connect to Gitlab.
6. github-actions commented on Jun 27, 2026

   

   github-actionsBot

   on Jun 27, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.
7. github-actions

   added

   Stale

   on Jun 27, 2026
8. github-actions commented on Jul 20, 2026

   

   github-actionsBot

   on Jul 20, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.
9. github-actions

   closed this as not plannedon Jul 20, 2026