Closed jberkus closed 3 years ago
Its sooooo simple. We just ignore github.com
in the gitlab
workers. I'll drop a patch in for this right away.
Sidebar: I almost made this very simply fix for a Pandas UNICODE patch we released today. The only thing more exciting than finding a weird bug (with NO ERROR) was discovering the LONG series of rants from other developers going back and forth the pandas team re: UNICODE, this error, and the appearance of everything being ok ... until you looked at your data. :D
OK, but there's the companion fact that the Github workers aren't collecting any data. Is that an unrelated issue?
@jberkus : This issue is resolved in our latest release I believe. This is the Unicode/Panda's very strange issue with Panda's to_sql()
method and Unicode.
I'm not sure this issue is fixed entirely. While the GH workers have restated, and are updating pull requests and contributors, we are still not getting any commit information. The commits may be a different issue, though, so opening that separately.
Regardless, I'm still seeing Gitlab errors in the log for Github repos:
2021-08-16 17:25:07,924 [PID: 2234862] augur.routes.broker [task_error() in broker.py:L218] [ERROR]: workers.gitlab_issues_worker.47921 ran into error while completing task: {'job_type': 'MAINTAIN', 'models': ['gitlab_issues'], 'display_name': 'gitlab_issues model for url: https://github.com/konveyor/move2kube-operator.git', 'given': {'git_url': 'https://github.com/konveyor/move2kube-operator.git'}, 'focused_task': 1, 'worker_id': 'workers.gitlab_issues_worker.47921'}
2021-08-16 17:25:23,019 [PID: 2234862] augur.routes.broker [task_error() in broker.py:L218] [ERROR]: workers.gitlab_issues_worker.47921 ran into error while completing task: {'job_type': 'MAINTAIN', 'models': ['gitlab_issues'], 'display_name': 'gitlab_issues model for url: https://github.com/konveyor/move2kube-demos.git', 'given': {'git_url': 'https://github.com/konveyor/move2kube-demos.git'}, 'focused_task': 1, 'worker_id': 'workers.gitlab_issues_worker.47921'}
This appears to be resolved with a rebuild of 20.2
Please help us help you by filling out the following sections as thoroughly as you can.
Description:
After an augur restart, errors with Github repo data collection get reported as gitlab worker errors. This appears to be because those Github repos have been handed to the gitlab_issue_worker for unknown reasons.
How to reproduce:
There are almost certainly additional conditions required to reproduce this issue but we don't at this point know what they are.
Expected behavior:
After restart, collecting data from GitHub for GitHub repositories should resume.
Log files
This, repeated every 15 seconds for lots of different repos:
Note that every one of those is a GitHub repository.
Checking the gitlab_issue_worker logs shows this:
... which shows us a data model error which I probably need to run a migration for, but it doesn't explain why the gitlab worker is handling this repo in the first place. Note that in issue #1349 I previously encountered this behavior under 0.17.0.
Software versions: