[Bug][Github] Incorrect datetime value: '0000-00-00' for column 'started_at'

[gbrancaglione]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

When running the pipeline against a github repo that was working normally, this started to appear. I don't know why this started. The other repos here (5+) are all working fine.

What do you expect to happen

I would expect this not to happen.

How to reproduce

I do not know how to reproduce it. The other projects are not having this error.

Anything else

No response

Version

v1.0.1

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

[dosubot]

Hello @gbrancaglione! I'm here to help you tackle any bugs, answer questions, and assist you in becoming a contributor while you wait for a human maintainer. Let's get to the bottom of this! 🤖

The MySQL error "Incorrect datetime value: '0000-00-00' for column 'started_at'" is likely caused by the StartedAt field in the DbCheckRun struct being set to a zero date value ('0000-00-00'). MySQL does not accept '0000-00-00' as a valid date unless the SQL mode is configured to allow it, which is not the default behavior.

To resolve this issue, ensure that the StartedAt field is initialized with a valid datetime value before it is inserted into the database. You can add a check in the Extract function to handle cases where checkRun.StartedAt is '0000-00-00' and set it to a valid default datetime or handle it according to your application's requirements. Here's a code snippet to handle this:

if checkRun.StartedAt == "0000-00-00" {
    checkRun.StartedAt = "1970-01-01" // or any other default valid datetime
}

This check should be added before the githubJob struct is created in the Extract function ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[klesh]

Try the latest beta. https://github.com/apache/incubator-devlake/releases/tag/v1.0.2-beta8

[zvika-finally]

This bug is related to #8214. It is solved, but it is not associated with any version. What's the procedure for adding it to a release?

[Joerg-Tech]

We've the same issue.
Would be nice to know for sure, which version or release-candidate will contain the fix.

[ivadimko]

Try the latest beta. v1.0.2-beta8 (release)

It fixed the initial sync (latest 14 days), but then I tried to get older data (last year) and it started failing again. Even in v1.0.2-beta8

[klesh]

Maybe we should skip those records without started_at value?
What do you guys think.

[ivadimko]

Maybe we should skip those records without started_at value? What do you guys think.

That sounds good. Is it possible to configure somehow directly while importing records? I've set 'skip failed tasks' after the initial sync and increased timeline from "last 14 days" to "last year". While showing 'partial success' in tasks it still doesn't update values in grafana dashboards (they show last 14 days).

What extra steps can I take to load only what loads correctly and see the full picture? Thank you in advance for your support

[dsiebel]

Try the latest beta. v1.0.2-beta8 (release)

It fixed the initial sync (latest 14 days), but then I tried to get older data (last year) and it started failing again. Even in v1.0.2-beta8

I can confirm this issue still exists in v1.0.2-beta9.

[Brend-Smits]

Also still exists in v1.0.3-beta1.
Can we skip records for now that have invalid date time?

[Brend-Smits]

Maybe we should skip those records without started_at value? What do you guys think.

I've opened a small PR with your proposed fix, would you be able to have a look at that please?
#8488