dosubot[bot] commented on issue #8689: URL: https://github.com/apache/incubator-devlake/issues/8689#issuecomment-3778405577
<!-- Greeting --> Hi @LucianoKratzer! I'm [Dosu](https://go.dosu.dev/dosubot) and Iām helping the incubator-devlake team. <!-- Answer --> This is a known limitation in how DevLake's GitHub plugin handles pull request status updates. Once a PR is closed or merged, the collector stops fetching its details for incremental updates, so the `status` field can remain stuck as `OPEN` even though `updated_at` advances with each pipeline run. This is why you see the timestamps update but not the status for many PRs, especially in high-volume environments. Recent changes improved status handling logic ([PR #8573](https://github.com/apache/incubator-devlake/pull/8573)), but if your deployment predates these, you may not have the fix. There are also related issues with merged and closed dates not updating for PRs that are closed, reopened, and then merged, due to how DevLake interacts with the GitHub API for closed/merged entities. This is documented as a known limitation in older versions and is not fixed there ([issue #8241](https://github.com/apache/incubator-devlake/issues/8241)). Upgrading to the latest version (at least v1.0.4-alpha or newer) should resolve several pipeline and data sync bugs, especially for high-volume repositories ([discussion](https://github.com/apache/incubator-devlake/issues/8538#issuecomment-3224132939)). For PRs already affected, a full re-collection (dropping and re-importing PR data) may be necessary to force status synchronization. Let me know if you want details on how to trigger a full re-collection or need help interpreting any other logs or behaviors. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/2b490dd0-fc37-410b-ad88-87e00a9653c6?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/2b490dd0-fc37-410b-ad88-87e00a9653c6?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/2b490dd0-fc37-410b-ad88-87e00a9653c6?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/2b490dd0-fc37-410b-ad88-87e00a9653c6?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/2b490dd0-fc37-410b-ad88-87e00a9653c6?feedback_type=hallucination) | [Report š](https://app.dosu.dev/response-feedback/2b490dd0-fc37-410b-ad88-87e00a9653c6?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/2b490dd0-fc37-410b-ad88-87e00a9653c6?feedback_type=other)</sup> [](https://app.dosu.dev/b4e8e847-d479-4541-83a8-d88d83fea5c9/ask?utm_source=github) [](https://cursor.com/link/prompt?text=This%20is%20a%20known%20limitation%20in%20how%20DevLake%27s%20GitHub%20plugin%20handles%20pull%20request%20status%20updates.%20Once%20a%20PR%20is%20closed%20or%20merged%2C%20the%20collector%20stops%20fetching%20its%20details%20for%20incremental%20updates%2C%20so%20the%20%60status%60%20field%20can%20remain%20stuck%20as%20%60OPEN%60%20even%20though%20%60updated_at%60%20advances%20with%20each%20pipeline%20run.%20This%20is%20why%20you%20see%20the%20timestamps%20update%20but%20not%20the%20status%20for%20many%20PRs%2C%20especially%20in%20high-volume%20environments.%20Recent%20changes%20improved%20status%20handling%20logic%20%28%5BPR%20%238573%5D%28https%3A//github.com/apache/incubator-devlake/pull/8573%29%29%2C%20but%20if%20your%20deployment%20predates%2 0these%2C%20you%20may%20not%20have%20the%20fix.%0A%0AThere%20are%20also%20related%20issues%20with%20merged%20and%20closed%20dates%20not%20updating%20for%20PRs%20that%20are%20closed%2C%20reopened%2C%20and%20then%20merged%2C%20due%20to%20how%20DevLake%20interacts%20with%20the%20GitHub%20API%20for%20closed/merged%20entities.%20This%20is%20documented%20as%20a%20known%20limitation%20in%20older%20versions%20and%20is%20not%20fixed%20there%20%28%5Bissue%20%238241%5D%28https%3A//github.com/apache/incubator-devlake/issues/8241%29%29.%0A%0AUpgrading%20to%20the%20latest%20version%20%28at%20least%20v1.0.4-alpha%20or%20newer%29%20should%20resolve%20several%20pipeline%20and%20data%20sync%20bugs%2C%20especially%20for%20high-volume%20repositories%20%28%5Bdiscussion%5D%28https%3A//github.com/apache/incubator-devlake/issues/8538%23issuecomment-3224132939%29%29.%20For%20PRs%20already%20affected%2C%20a%20full%20re-collection%20%28dropping%20and%20re-importing%20PR%20data%29%20may%20be%20necessary%20to%2 0force%20status%20synchronization.%0A%0ALet%20me%20know%20if%20you%20want%20details%20on%20how%20to%20trigger%20a%20full%20re-collection%20or%20need%20help%20interpreting%20any%20other%20logs%20or%20behaviors.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/incubator-devlake/issues/8689) -- 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]
