This is an automated email from the ASF dual-hosted git repository.
abeizn pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-devlake-website.git
The following commit(s) were added to refs/heads/main by this push:
new b43b034638 fix: update the spelling for GitLab (#662)
b43b034638 is described below
commit b43b034638b027d1c2afdfca86a690f19afad1cf
Author: Louis.z <[email protected]>
AuthorDate: Wed Oct 18 18:03:28 2023 +0800
fix: update the spelling for GitLab (#662)
Co-authored-by: Startrekzky <[email protected]>
---
.../index.md | 2 +-
docs/DataModels/DevLakeDomainLayerSchema.md | 14 +++++++-------
docs/Overview/SupportedDataSources.md | 2 +-
docs/Troubleshooting/Configuration.md | 2 +-
versioned_docs/version-v0.11/DataModels/DataSupport.md | 2 +-
.../version-v0.18/DataModels/DevLakeDomainLayerSchema.md | 14 +++++++-------
.../version-v0.18/Overview/SupportedDataSources.md | 2 +-
.../version-v0.18/Troubleshooting/Configuration.md | 2 +-
.../version-v0.19/DataModels/DevLakeDomainLayerSchema.md | 14 +++++++-------
.../version-v0.19/Overview/SupportedDataSources.md | 2 +-
.../version-v0.19/Troubleshooting/Configuration.md | 2 +-
11 files changed, 29 insertions(+), 29 deletions(-)
diff --git
a/blog/2022-06-23-compatibility-of-apache-devLake-with-postgreSQL/index.md
b/blog/2022-06-23-compatibility-of-apache-devLake-with-postgreSQL/index.md
index 92475271e1..855dec2c25 100644
--- a/blog/2022-06-23-compatibility-of-apache-devLake-with-postgreSQL/index.md
+++ b/blog/2022-06-23-compatibility-of-apache-devLake-with-postgreSQL/index.md
@@ -5,7 +5,7 @@ authors: ZhangLiang
tags: [devlake, database, postgresql]
---
-Apache DevLake is a dev data platform that can collect and integrate data from
different dev tools including Jira, Github, Gitlab and Jenkins.
+Apache DevLake is a dev data platform that can collect and integrate data from
different dev tools including Jira, Github, GitLab and Jenkins.
This blog will not aim at a comprehensive summary of the compatibility of
database but a record of issues for future reference.
diff --git a/docs/DataModels/DevLakeDomainLayerSchema.md
b/docs/DataModels/DevLakeDomainLayerSchema.md
index 88f8889fbb..069d28b2b0 100644
--- a/docs/DataModels/DevLakeDomainLayerSchema.md
+++ b/docs/DataModels/DevLakeDomainLayerSchema.md
@@ -15,7 +15,7 @@ sidebar_position: 1
This document describes Apache DevLake's domain layer schema.
-Referring to DevLake's [architecture](../Overview/Architecture.md), the data
in the domain layer is transformed from the data in the tool layer. The tool
layer schema is based on the data from specific tools such as Jira, GitHub,
Gitlab, Jenkins, etc. The domain layer schema can be regarded as an abstraction
of tool-layer schemas.
+Referring to DevLake's [architecture](../Overview/Architecture.md), the data
in the domain layer is transformed from the data in the tool layer. The tool
layer schema is based on the data from specific tools such as Jira, GitHub,
GitLab, Jenkins, etc. The domain layer schema can be regarded as an abstraction
of tool-layer schemas.
<p align="center"><img src="/img/Architecture/arch-dataflow.svg" /></p>
<p align="center">DevLake Dataflow</p>
@@ -31,8 +31,8 @@ Referring to DevLake's
[architecture](../Overview/Architecture.md), the data in
This is the up-to-date domain layer schema for DevLake. Tables (entities) are
categorized into 5 domains.
1. Issue tracking: Jira issues, GitHub issues, GitLab issues, etc.
-2. Source code management: Git/GitHub/Gitlab commits and refs(tags and
branches), etc.
-3. Code review: GitHub PRs, Gitlab MRs, etc.
+2. Source code management: Git/GitHub/GitLab commits and refs(tags and
branches), etc.
+3. Code review: GitHub PRs, GitLab MRs, etc.
4. CI/CD: Jenkins jobs & builds, etc.
5. Code Quality: SonarQube issues, hotspots, file metrics, etc.
6. Cross-domain: entities that map entities from different domains to break
data isolation.
@@ -41,7 +41,7 @@ This is the up-to-date domain layer schema for DevLake.
Tables (entities) are ca
-When reading the schema, you'll notice that many tables' primary key is called
`id`. Unlike auto-increment id or UUID, `id` is a string composed of several
parts to uniquely identify similar entities (e.g. repo) from different
platforms (e.g. Github/Gitlab) and allow them to co-exist in a single table.
+When reading the schema, you'll notice that many tables' primary key is called
`id`. Unlike auto-increment id or UUID, `id` is a string composed of several
parts to uniquely identify similar entities (e.g. repo) from different
platforms (e.g. Github/GitLab) and allow them to co-exist in a single table.
Tables that end with WIP are still under development.
@@ -84,7 +84,7 @@ An `issue` is the abstraction of
Github/GitLab/BitBucket/Jira/TAPD/Zentao... iss
| `component` | varchar | 255 | The component a
bug-issue affects. This field only supports Github plugin for now. The value is
transformed from Github issue labels by the rules set according to the user's
configuration of .env by end users during DevLake installation.
[...]
| `severity` | varchar | 255 | The severity level of
a bug-issue. This field only supports Github plugin for now. The value is
transformed from Github issue labels by the rules set according to the user's
configuration of .env by end users during DevLake installation.
[...]
| `parent_issue_id` | varchar | 255 | The id of its parent
issue
[...]
-| `epic_key` | varchar | 255 | The key of the epic
this issue belongs to. For tools with no epic-type issues such as Github and
Gitlab, this field is default to an empty string
[...]
+| `epic_key` | varchar | 255 | The key of the epic
this issue belongs to. For tools with no epic-type issues such as Github and
GitLab, this field is default to an empty string
[...]
| `original_estimate_minutes` | int | | The original
estimation of the time allocated for this issue
[...]
| `time_spent_minutes` | int | | The original
estimation of the time allocated for this issue
[...]
| `time_remaining_minutes` | int | | The remaining time to
resolve the issue
[...]
@@ -246,7 +246,7 @@ This table shows the relation between sprints and issues
that have been added to
#### repos
-GitHub, Gitlab or BitBucket repositories.
+GitHub, GitLab or BitBucket repositories.
| **field** | **type** | **length** | **description**
| **key** |
| :------------- | :------- | :--------- |
:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| :------------- |
@@ -386,7 +386,7 @@ Pull requests are the abstraction of GitHub pull requests,
GitLab merge requests
| `author_id` | varchar | 100 | The author's id of the pull
request
| |
| `url` | varchar | 255 | the web link of the pull
request
| |
| `type` | varchar | 255 | The work-type of a pull
request.For example: feature-development, bug-fix, docs,etc.
| |
-| `component` | varchar | 255 | The component this PR
affects.<br/>The value is transformed from Github/Gitlab pull request labels by
configuring `GITHUB_PR_COMPONENT` in `.env` file during installation.
| |
+| `component` | varchar | 255 | The component this PR
affects.<br/>The value is transformed from Github/GitLab pull request labels by
configuring `GITHUB_PR_COMPONENT` in `.env` file during installation.
| |
| `created_date` | datetime | 3 | The time PR created.
| |
| `merged_date` | datetime | 3 | The time PR gets merged. Null
when the PR is not merged.
| |
| `closed_date` | datetime | 3 | The time PR closed. Null when
the PR is not closed.
| |
diff --git a/docs/Overview/SupportedDataSources.md
b/docs/Overview/SupportedDataSources.md
index 232f9d220b..4b95aaf95d 100644
--- a/docs/Overview/SupportedDataSources.md
+++ b/docs/Overview/SupportedDataSources.md
@@ -115,7 +115,7 @@ This table shows the entities collected by each plugin.
Domain layer entities in
| CollectApiBuildsMeta | ≈100 | ❌
| ❌ |
| CollectApiStagesMeta | ≈10^4 | ❌
| ✅ |
-### Gitlab
+### GitLab
| Subtask Name | Estimated Max Number of Request | Does It
support Incremental Collection? | Does It Support Time Filter? |
| --------------------------- | ------------------------------- |
--------------------------------------- | ---------------------------- |
diff --git a/docs/Troubleshooting/Configuration.md
b/docs/Troubleshooting/Configuration.md
index d998cebcd7..e440af452a 100644
--- a/docs/Troubleshooting/Configuration.md
+++ b/docs/Troubleshooting/Configuration.md
@@ -49,7 +49,7 @@ This bug happens occasionally in v0.14.x and previous
versions. It is fixed by c
We have had a couple of reports suggesting MySQL InnoDB would fail with the
message.
- [Error 1206: The total number of locks exceeds the lock table size · Issue
#3849 ·
apache/incubator-devlake](https://github.com/apache/incubator-devlake/issues/3849)
-- [[Bug][Gitlab] gitlab collectApiJobs task failed for mysql locks error ·
Issue #3653 ·
apache/incubator-devlake](https://github.com/apache/incubator-devlake/issues/3653)
+- [[Bug][GitLab] gitlab collectApiJobs task failed for mysql locks error ·
Issue #3653 ·
apache/incubator-devlake](https://github.com/apache/incubator-devlake/issues/3653)
The cause of the problem is:
diff --git a/versioned_docs/version-v0.11/DataModels/DataSupport.md
b/versioned_docs/version-v0.11/DataModels/DataSupport.md
index 4cb4b61913..6cb180afea 100644
--- a/versioned_docs/version-v0.11/DataModels/DataSupport.md
+++ b/versioned_docs/version-v0.11/DataModels/DataSupport.md
@@ -15,7 +15,7 @@ DevLake supports the following data sources. The data from
each data source is c
| AE | | `ae` |
| Feishu | Cloud |`feishu` |
| GitHub | Cloud |`github`,
`gitextractor`, `refdiff` |
-| Gitlab | Cloud, Community Edition 13.x+ |`gitlab`,
`gitextractor`, `refdiff` |
+| GitLab | Cloud, Community Edition 13.x+ |`gitlab`,
`gitextractor`, `refdiff` |
| Jenkins | 2.263.x+ |`jenkins` |
| Jira | Cloud, Server 8.x+, Data Center 8.x+ |`jira` |
| TAPD | Cloud | `tapd` |
diff --git
a/versioned_docs/version-v0.18/DataModels/DevLakeDomainLayerSchema.md
b/versioned_docs/version-v0.18/DataModels/DevLakeDomainLayerSchema.md
index b3ce666357..e70a8dac4f 100644
--- a/versioned_docs/version-v0.18/DataModels/DevLakeDomainLayerSchema.md
+++ b/versioned_docs/version-v0.18/DataModels/DevLakeDomainLayerSchema.md
@@ -16,7 +16,7 @@ sidebar_position: 1
This document describes Apache DevLake's domain layer schema.
-Referring to DevLake's [architecture](../Overview/Architecture.md), the data
in the domain layer is transformed from the data in the tool layer. The tool
layer schema is based on the data from specific tools such as Jira, GitHub,
Gitlab, Jenkins, etc. The domain layer schema can be regarded as an abstraction
of tool-layer schemas.
+Referring to DevLake's [architecture](../Overview/Architecture.md), the data
in the domain layer is transformed from the data in the tool layer. The tool
layer schema is based on the data from specific tools such as Jira, GitHub,
GitLab, Jenkins, etc. The domain layer schema can be regarded as an abstraction
of tool-layer schemas.
<p align="center"><img src="/img/Architecture/arch-dataflow.svg" /></p>
<p align="center">DevLake Dataflow</p>
@@ -32,8 +32,8 @@ Referring to DevLake's
[architecture](../Overview/Architecture.md), the data in
This is the up-to-date domain layer schema for DevLake. Tables (entities) are
categorized into 5 domains.
1. Issue tracking: Jira issues, GitHub issues, GitLab issues, etc.
-2. Source code management: Git/GitHub/Gitlab commits and refs(tags and
branches), etc.
-3. Code review: GitHub PRs, Gitlab MRs, etc.
+2. Source code management: Git/GitHub/GitLab commits and refs(tags and
branches), etc.
+3. Code review: GitHub PRs, GitLab MRs, etc.
4. CI/CD: Jenkins jobs & builds, etc.
5. Code Quality: SonarQube issues, hotspots, file metrics, etc.
6. Cross-domain: entities that map entities from different domains to break
data isolation.
@@ -42,7 +42,7 @@ This is the up-to-date domain layer schema for DevLake.
Tables (entities) are ca
-When reading the schema, you'll notice that many tables' primary key is called
`id`. Unlike auto-increment id or UUID, `id` is a string composed of several
parts to uniquely identify similar entities (e.g. repo) from different
platforms (e.g. Github/Gitlab) and allow them to co-exist in a single table.
+When reading the schema, you'll notice that many tables' primary key is called
`id`. Unlike auto-increment id or UUID, `id` is a string composed of several
parts to uniquely identify similar entities (e.g. repo) from different
platforms (e.g. Github/GitLab) and allow them to co-exist in a single table.
Tables that end with WIP are still under development.
@@ -85,7 +85,7 @@ An `issue` is the abstraction of
Github/GitLab/BitBucket/Jira/TAPD/Zentao... iss
| `component` | varchar | 255 | The component a
bug-issue affects. This field only supports Github plugin for now. The value is
transformed from Github issue labels by the rules set according to the user's
configuration of .env by end users during DevLake installation.
[...]
| `severity` | varchar | 255 | The severity level of
a bug-issue. This field only supports Github plugin for now. The value is
transformed from Github issue labels by the rules set according to the user's
configuration of .env by end users during DevLake installation.
[...]
| `parent_issue_id` | varchar | 255 | The id of its parent
issue
[...]
-| `epic_key` | varchar | 255 | The key of the epic
this issue belongs to. For tools with no epic-type issues such as Github and
Gitlab, this field is default to an empty string
[...]
+| `epic_key` | varchar | 255 | The key of the epic
this issue belongs to. For tools with no epic-type issues such as Github and
GitLab, this field is default to an empty string
[...]
| `original_estimate_minutes` | int | | The original
estimation of the time allocated for this issue
[...]
| `time_spent_minutes` | int | | The original
estimation of the time allocated for this issue
[...]
| `time_remaining_minutes` | int | | The remaining time to
resolve the issue
[...]
@@ -236,7 +236,7 @@ This table shows the relation between sprints and issues
that have been added to
#### repos
-GitHub, Gitlab or BitBucket repositories.
+GitHub, GitLab or BitBucket repositories.
| **field** | **type** | **length** | **description**
| **key** |
| :------------- | :------- | :--------- |
:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| :------------- |
@@ -376,7 +376,7 @@ Pull requests are the abstraction of GitHub pull requests,
GitLab merge requests
| `author_id` | varchar | 100 | The author's id of the pull
request
| |
| `url` | varchar | 255 | the web link of the pull
request
| |
| `type` | varchar | 255 | The work-type of a pull
request.For example: feature-development, bug-fix, docs,etc.
| |
-| `component` | varchar | 255 | The component this PR
affects.<br/>The value is transformed from Github/Gitlab pull request labels by
configuring `GITHUB_PR_COMPONENT` in `.env` file during installation.
| |
+| `component` | varchar | 255 | The component this PR
affects.<br/>The value is transformed from Github/GitLab pull request labels by
configuring `GITHUB_PR_COMPONENT` in `.env` file during installation.
| |
| `created_date` | datetime | 3 | The time PR created.
| |
| `merged_date` | datetime | 3 | The time PR gets merged. Null
when the PR is not merged.
| |
| `closed_date` | datetime | 3 | The time PR closed. Null when
the PR is not closed.
| |
diff --git a/versioned_docs/version-v0.18/Overview/SupportedDataSources.md
b/versioned_docs/version-v0.18/Overview/SupportedDataSources.md
index 232f9d220b..4b95aaf95d 100644
--- a/versioned_docs/version-v0.18/Overview/SupportedDataSources.md
+++ b/versioned_docs/version-v0.18/Overview/SupportedDataSources.md
@@ -115,7 +115,7 @@ This table shows the entities collected by each plugin.
Domain layer entities in
| CollectApiBuildsMeta | ≈100 | ❌
| ❌ |
| CollectApiStagesMeta | ≈10^4 | ❌
| ✅ |
-### Gitlab
+### GitLab
| Subtask Name | Estimated Max Number of Request | Does It
support Incremental Collection? | Does It Support Time Filter? |
| --------------------------- | ------------------------------- |
--------------------------------------- | ---------------------------- |
diff --git a/versioned_docs/version-v0.18/Troubleshooting/Configuration.md
b/versioned_docs/version-v0.18/Troubleshooting/Configuration.md
index fbe71e76c3..02bc49263f 100644
--- a/versioned_docs/version-v0.18/Troubleshooting/Configuration.md
+++ b/versioned_docs/version-v0.18/Troubleshooting/Configuration.md
@@ -49,7 +49,7 @@ This bug happens occasionally in v0.14.x and previous
versions. It is fixed by c
We have had a couple of reports suggesting MySQL InnoDB would fail with the
message.
- [Error 1206: The total number of locks exceeds the lock table size · Issue
#3849 ·
apache/incubator-devlake](https://github.com/apache/incubator-devlake/issues/3849)
-- [[Bug][Gitlab] gitlab collectApiJobs task failed for mysql locks error ·
Issue #3653 ·
apache/incubator-devlake](https://github.com/apache/incubator-devlake/issues/3653)
+- [[Bug][GitLab] gitlab collectApiJobs task failed for mysql locks error ·
Issue #3653 ·
apache/incubator-devlake](https://github.com/apache/incubator-devlake/issues/3653)
The cause of the problem is:
diff --git
a/versioned_docs/version-v0.19/DataModels/DevLakeDomainLayerSchema.md
b/versioned_docs/version-v0.19/DataModels/DevLakeDomainLayerSchema.md
index 88f8889fbb..069d28b2b0 100644
--- a/versioned_docs/version-v0.19/DataModels/DevLakeDomainLayerSchema.md
+++ b/versioned_docs/version-v0.19/DataModels/DevLakeDomainLayerSchema.md
@@ -15,7 +15,7 @@ sidebar_position: 1
This document describes Apache DevLake's domain layer schema.
-Referring to DevLake's [architecture](../Overview/Architecture.md), the data
in the domain layer is transformed from the data in the tool layer. The tool
layer schema is based on the data from specific tools such as Jira, GitHub,
Gitlab, Jenkins, etc. The domain layer schema can be regarded as an abstraction
of tool-layer schemas.
+Referring to DevLake's [architecture](../Overview/Architecture.md), the data
in the domain layer is transformed from the data in the tool layer. The tool
layer schema is based on the data from specific tools such as Jira, GitHub,
GitLab, Jenkins, etc. The domain layer schema can be regarded as an abstraction
of tool-layer schemas.
<p align="center"><img src="/img/Architecture/arch-dataflow.svg" /></p>
<p align="center">DevLake Dataflow</p>
@@ -31,8 +31,8 @@ Referring to DevLake's
[architecture](../Overview/Architecture.md), the data in
This is the up-to-date domain layer schema for DevLake. Tables (entities) are
categorized into 5 domains.
1. Issue tracking: Jira issues, GitHub issues, GitLab issues, etc.
-2. Source code management: Git/GitHub/Gitlab commits and refs(tags and
branches), etc.
-3. Code review: GitHub PRs, Gitlab MRs, etc.
+2. Source code management: Git/GitHub/GitLab commits and refs(tags and
branches), etc.
+3. Code review: GitHub PRs, GitLab MRs, etc.
4. CI/CD: Jenkins jobs & builds, etc.
5. Code Quality: SonarQube issues, hotspots, file metrics, etc.
6. Cross-domain: entities that map entities from different domains to break
data isolation.
@@ -41,7 +41,7 @@ This is the up-to-date domain layer schema for DevLake.
Tables (entities) are ca
-When reading the schema, you'll notice that many tables' primary key is called
`id`. Unlike auto-increment id or UUID, `id` is a string composed of several
parts to uniquely identify similar entities (e.g. repo) from different
platforms (e.g. Github/Gitlab) and allow them to co-exist in a single table.
+When reading the schema, you'll notice that many tables' primary key is called
`id`. Unlike auto-increment id or UUID, `id` is a string composed of several
parts to uniquely identify similar entities (e.g. repo) from different
platforms (e.g. Github/GitLab) and allow them to co-exist in a single table.
Tables that end with WIP are still under development.
@@ -84,7 +84,7 @@ An `issue` is the abstraction of
Github/GitLab/BitBucket/Jira/TAPD/Zentao... iss
| `component` | varchar | 255 | The component a
bug-issue affects. This field only supports Github plugin for now. The value is
transformed from Github issue labels by the rules set according to the user's
configuration of .env by end users during DevLake installation.
[...]
| `severity` | varchar | 255 | The severity level of
a bug-issue. This field only supports Github plugin for now. The value is
transformed from Github issue labels by the rules set according to the user's
configuration of .env by end users during DevLake installation.
[...]
| `parent_issue_id` | varchar | 255 | The id of its parent
issue
[...]
-| `epic_key` | varchar | 255 | The key of the epic
this issue belongs to. For tools with no epic-type issues such as Github and
Gitlab, this field is default to an empty string
[...]
+| `epic_key` | varchar | 255 | The key of the epic
this issue belongs to. For tools with no epic-type issues such as Github and
GitLab, this field is default to an empty string
[...]
| `original_estimate_minutes` | int | | The original
estimation of the time allocated for this issue
[...]
| `time_spent_minutes` | int | | The original
estimation of the time allocated for this issue
[...]
| `time_remaining_minutes` | int | | The remaining time to
resolve the issue
[...]
@@ -246,7 +246,7 @@ This table shows the relation between sprints and issues
that have been added to
#### repos
-GitHub, Gitlab or BitBucket repositories.
+GitHub, GitLab or BitBucket repositories.
| **field** | **type** | **length** | **description**
| **key** |
| :------------- | :------- | :--------- |
:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| :------------- |
@@ -386,7 +386,7 @@ Pull requests are the abstraction of GitHub pull requests,
GitLab merge requests
| `author_id` | varchar | 100 | The author's id of the pull
request
| |
| `url` | varchar | 255 | the web link of the pull
request
| |
| `type` | varchar | 255 | The work-type of a pull
request.For example: feature-development, bug-fix, docs,etc.
| |
-| `component` | varchar | 255 | The component this PR
affects.<br/>The value is transformed from Github/Gitlab pull request labels by
configuring `GITHUB_PR_COMPONENT` in `.env` file during installation.
| |
+| `component` | varchar | 255 | The component this PR
affects.<br/>The value is transformed from Github/GitLab pull request labels by
configuring `GITHUB_PR_COMPONENT` in `.env` file during installation.
| |
| `created_date` | datetime | 3 | The time PR created.
| |
| `merged_date` | datetime | 3 | The time PR gets merged. Null
when the PR is not merged.
| |
| `closed_date` | datetime | 3 | The time PR closed. Null when
the PR is not closed.
| |
diff --git a/versioned_docs/version-v0.19/Overview/SupportedDataSources.md
b/versioned_docs/version-v0.19/Overview/SupportedDataSources.md
index 232f9d220b..4b95aaf95d 100644
--- a/versioned_docs/version-v0.19/Overview/SupportedDataSources.md
+++ b/versioned_docs/version-v0.19/Overview/SupportedDataSources.md
@@ -115,7 +115,7 @@ This table shows the entities collected by each plugin.
Domain layer entities in
| CollectApiBuildsMeta | ≈100 | ❌
| ❌ |
| CollectApiStagesMeta | ≈10^4 | ❌
| ✅ |
-### Gitlab
+### GitLab
| Subtask Name | Estimated Max Number of Request | Does It
support Incremental Collection? | Does It Support Time Filter? |
| --------------------------- | ------------------------------- |
--------------------------------------- | ---------------------------- |
diff --git a/versioned_docs/version-v0.19/Troubleshooting/Configuration.md
b/versioned_docs/version-v0.19/Troubleshooting/Configuration.md
index 1a4becda59..3fb10eafe7 100644
--- a/versioned_docs/version-v0.19/Troubleshooting/Configuration.md
+++ b/versioned_docs/version-v0.19/Troubleshooting/Configuration.md
@@ -49,7 +49,7 @@ This bug happens occasionally in v0.14.x and previous
versions. It is fixed by c
We have had a couple of reports suggesting MySQL InnoDB would fail with the
message.
- [Error 1206: The total number of locks exceeds the lock table size · Issue
#3849 ·
apache/incubator-devlake](https://github.com/apache/incubator-devlake/issues/3849)
-- [[Bug][Gitlab] gitlab collectApiJobs task failed for mysql locks error ·
Issue #3653 ·
apache/incubator-devlake](https://github.com/apache/incubator-devlake/issues/3653)
+- [[Bug][GitLab] gitlab collectApiJobs task failed for mysql locks error ·
Issue #3653 ·
apache/incubator-devlake](https://github.com/apache/incubator-devlake/issues/3653)
The cause of the problem is:
