Closed mkaufmaner closed 3 weeks ago
Are error messages when you "hover to view the reason" the same with devlake-github-500.json?
Because I cann't find useful info from the json file(not your problem, the error messages are too mess). @mkaufmaner
Are error messages when you "hover to view the reason" the same with devlake-github-500.json?
Because I cann't find useful info from the json file(not your problem, the error messages are too mess).
@mkaufmaner
Yes, they are.
I am trying to get the logs but when the pod restarted with the updated nginx configuration the logs got blown away. Rerunning the task now to get the logs. Will probably take a few minutes.
@d4x1 Updated the main bug report with the full log for the failed github task. Uncompressed they are 32.7MB. See https://github.com/apache/incubator-devlake/files/13178290/task-129911-2-1-github.log.zip
@d4x1 Upon further investigation, it appears to be due to a resource limitation on our GHE server and the requests are timing out. Wish we could get graphql working, which we may get working after upgrading our GHE to the latest stable version of 3.10, but that is TBD.
Side note; is there a client side request timeout I should be worried about? I tried looking through the source code and documentation but couldn't find anything.
The default timeout of GitHub graphql is 30s
, but you can change it by setting an Env Var named API_TIMEOUT
, keep in mind the s
part is required, you can specify s
for seconds, m
for minutes and h
for hours.
This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.
This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.
This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.
This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.
This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.
Closed due to inactivity,
Search before asking
What happened
The GitHub plugin pipeline task for a GitHub repository with;
Full Logs (Sanitized): task-129911-2-1-github.log.zip
Simplified Task JSON:
Full Task JSON (1.2MB): devlake-github-500.json
Screenshot:
What do you expect to happen
I expected this task to be successful.
How to reproduce
This is a good question, I am guessing with a repository with a significant amount of PRs and commits.
Anything else
Possibly related to https://github.com/apache/incubator-devlake/issues/6320
Version
v0.18.0
Are you willing to submit PR?
Code of Conduct