klesh commented on issue #7739: URL: https://github.com/apache/incubator-devlake/issues/7739#issuecomment-2259989887
> > > Yes @klesh these workflows ran in April current year. I even tried from the GitHub API and it brings me all the workflows without any problem. > > > > > > @daviddsp Can you check the raw and tool layer tables' data? They should have all workflows (384 in your case). > > @d4x1 Yes, I checked table _raw_github_api_runs, and doesn't this total of pipelines that return Github API, I tried to test this in different Devlake versions, and this lost data in v20.0 and v.21.0, test with versions 18.0 and 17.0, and works perfectly. Sorry? What was the number of total records in the `_raw_github_api_runs` for v0.20 and 0.21? > @d4x1, thank you very much. I really want to resolve this issue. > > I reviewed the code in this specific version of DevLake and understand that this filter only includes actions with a **"completed"** status. I have tested this and will share a new screenshot when the table **`SELECT * FROM _tool_github_runs;`** only contains records with a **"completed"** status. > > For Slack, I recommend running this query. It is quite strange because it does not return any records with a status other than "completed" in the table **`_raw_github_api_runs`**. Perhaps the change you mentioned has been implemented, resulting in the deletion of pipelines with statuses other than **"completed"**. > > And in always delete my database when change to other version of Devlake for just to avoid compatibility problems. > > Now in github have these total of workflows, i will separate for status: > > * waiting: 1. > * completed: 1.334. > * failure: 470. > * cancelled: 16. > I don't understand the figures here. If all those missing runs were **NOT** `completed` records such as `pending`, then the result of their being deleted is expected. because it has no point to analyze them. -- 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: dev-unsubscr...@devlake.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
