Repository navigation
[Bug][Github Data Collection] Receiving Incorrect datetime value: '0000-00-00' for column 'started_at' at row 280 Error types for some data collection in Github #8538
Description
Search before asking
- I had searched in the issues and found no similar issues.
What happened
Receiving the below error while trying collecting the data from few Github Repositories
subtask Extract Jobs ended unexpectedly Wraps: (2) error adding result to batch (500) Wraps: (3) Error 1292 (22007): Incorrect datetime value: '0000-00-00' for column 'started_at' at row 280 (500) Wraps: (4) Error 1292 (22007): Incorrect datetime value: '0000-00-00' for column 'started_at' at row 280 Error types: (1) *hintdetail.withDetail (2) *hintdetail.withDetail (3) *hintdetail.withDetail (4) *mysql.MySQLError
What do you expect to happen
Dev lake data collection pipeline should not fail and expecting the data collection to work fine.
How to reproduce
It's working for most of the repositories, but we're seeing failures on a few of them.
Anything else
Issue discussion @ https://devlake-io.slack.com/archives/C03APJ20VM4/p1754475976018429
if you need issue logs, let us know
Version
devlake:v1.0.2-beta8
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct
Activity
petkostas commentedon Aug 14, 2025
Most likely related to #8442
klesh commentedon Aug 22, 2025
Hi, @Startrekzky, I just reassigned the issue to @petkostas because he has been working on it for a while.
ssasoglu commentedon Aug 26, 2025
It looks like this was addressed in #8536 but there is no beta release that has this fix included. When can we get one @klesh? Or is this another bug on top of the solution?
petkostas commentedon Aug 26, 2025
@ssasoglu the merged PR addresses the issue in one place, but the remaining fields and tasks also need updating. I've opened a new PR to handle these changes. I'm currently looking for a few repositories that replicate the zero-time behavior, which is a corner case, to ensure the fix works as expected.
I'll provide an update once I've verified the fix with these additional cases.
petkostas commentedon Sep 1, 2025
I am currently testing this with a few repositories, but I haven't been able to reproduce a zero-time date yet. My next step will be to create some tests that cover this scenario. Alternatively, if anyone affected by this issue can replicate the database and test against my branch, that would be very helpful.
ssasoglu commentedon Sep 8, 2025
@petkostas would it be a good idea to create an alpha version out of your branch? Otherwise we need to go through the developer setup right?
If we can get our hands on an alpha release, we can test it against the repo that we are having issues with.
klesh commentedon Sep 10, 2025
@petkostas You now have write access, so you can push the new branch directly to the main repo.
Pushing a
tagthat starts withv(e.g.,v1.0.4-alpha) will trigger the GitHub Action to build docker imagespetkostas commentedon Sep 12, 2025
Thanks @klesh! I will most likely push next week as I am currently blocked for personal reasons.
petkostas commentedon Sep 22, 2025
@ssasoglu I have created a new PR directly to Devlake with the tag
v1.0.4-alphathe images should be ready, can you give it a go?@klesh there was a lint error in an existing migration file (whitespace), I have included a fix as a separate commit (the file was not modified by my original changes).
klesh commentedon Sep 25, 2025
Got it, thanks for the information.
ssasoglu commentedon Sep 30, 2025
The NPM supply chain attack degraded our availability to test the new alpha version.
We are back in full capacity now. We will try
v1.0.4-alphaversion in the following days and I will update here.ssasoglu commentedon Oct 1, 2025
We confirmed that
v1.0.4-alphafixes this issue. The repository we had problems before, didn't have any problems with the pipeline in this version! Thank you for the effort. 🙌klesh commentedon Oct 9, 2025
@ssasoglu @petkostas Thanks for your contribution.