dosubot[bot] commented on issue #8848: URL: https://github.com/apache/incubator-devlake/issues/8848#issuecomment-4310593808
<!-- Greeting --> Hi @nkofficial-1005! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the incubator-devlake team. <!-- Answer --> This is a documented bug where the `ConvertRelease` function panics because the `PublishedAt` field on a `GithubRelease` can be nil (it was a `*time.Time` pointer type), and the converter dereferences it without a nil check [[1]](https://github.com/apache/incubator-devlake/blob/2c15ad880dce830c6512fa58039527cbf4745b8b/backend/plugins/github/tasks/release_convertor.go#L70-L96). Draft releases from GitHub have no `PublishedAt` value, which triggers the panic. PR #8628 reported a **100% failure rate** for all repositories with releases at this step [[2]](https://github.com/apache/incubator-devlake/pull/8628). This has been addressed in more recent versions through multiple fixes: - **PR #8583** introduced a `NilIfZeroTime` utility to normalize nil/zero time values across the GitHub plugin [[3]](https://github.com/apache/incubator-devlake/pull/8583). - **PR #8625** added database-level filtering for draft releases [[4]](https://github.com/apache/incubator-devlake/pull/8625). - The `PublishedAt` field was eventually changed from `*time.Time` (pointer) to `time.Time` (value type), eliminating the nil dereference entirely [[5]](https://github.com/apache/incubator-devlake/blob/2c15ad880dce830c6512fa58039527cbf4745b8b/backend/plugins/github/models/release.go#L41). **To answer your specific questions:** 1. Yes, this was a bug that has been fixed in newer versions. Upgrading from v1.0.4-alpha should resolve it. 2. Skipping release subtasks is a valid workaround (as you've already discovered). 3. Yes — the nil pointer at line 76 is specifically caused by releases with a nil `PublishedAt` (e.g., draft releases). 4. It is safe to run without release collection. DORA metrics rely on deployments and PRs/incidents, not GitHub Releases, so skipping release subtasks will not affect DORA calculations. **Recommendation:** Upgrade to a newer version of DevLake where this is fixed. If you must stay on v1.0.4-alpha, your workaround of skipping the release subtasks is the right approach. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fincubator-devlake).* --- Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fincubator-devlake). [](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fincubator-devlake#message_id=a74b2efb-b598-473f-9bc8-b30d9078bc24) [](https://github.dosu.com/apache/incubator-devlake?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fincubator-devlake) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fincubator-devlake) -- 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]
