mindspop opened a new issue, #6764: URL: https://github.com/apache/incubator-devlake/issues/6764
### 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 When synchronizing devLake and GitLab data, the synchronization task failed (the error is as follows). subtask ExtractDeployment ended unexpectedly Wraps: (2) error adding result to batch (500) Wraps: (3) Error 1292 (22007): Incorrect datetime value: '0000-00-00' for column 'deployable_user_created_at' at row 9 (500) Wraps: (4) Error 1292 (22007): Incorrect datetime value: '0000-00-00' for column 'deployable_user_created_at' at row 9 Error types: (1) *hintdetail.withDetail (2) *hintdetail.withDetail (3) *hintdetail.withDetail (4) *mysql.MySQLError <img width="811" alt="image" src="https://github.com/apache/incubator-devlake/assets/8045506/7b9f5caf-15d0-4deb-883e-ef36202ea8ae";> ### What do you expect to happen Data synchronization can be performed normally. ### How to reproduce Configure data synchronization for GitLab, including deployment data and having the deployment user account in a blocked state. install method: docker-compose GitLab version: 15.2.2-ee ### Anything else After investigation, it was found that the interface returned by the GitLab API(api/v4/projects/1/deployments/:id) lacks the field deployable.user.created_at (when the user is in a blocked state, this field is not returned), and the devLake GitLab plugin [requires this field to be required](https://github.com/apache/incubator-devlake/blob/013fe67642049a799f2eef352c53288240eacf39/backend/plugins/gitlab/models/deployment.go#L71). ### Version v0.20.0-beta5 ### 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
