-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UNABLE TO FETCH WORKFLOWS #270
Comments
Looks like you nare giving |
I have reproduced the issue locally, a fix is on the way. Since the new release failed halfway I need to look into excluding SQLite for some os or architectures. |
The |
Thank you so much. It works now |
Sadly no final release yet, still got issues while building everything. |
Finally I have released 3.0.1 now! 🥳 |
🥳. I tried it now sir. and the workflow metrics are no more populating 🙁. No error in the logs though. v3 works |
Have you also deleted the database file to start from the scratch? |
How do I do that |
Depends on how you deployed it. If you have enabled persistence replace the volume, if you haven't make sure the pods are getting deleted to create a new empty dir volume |
I am not using a persitent volume. The have recreated the pods numerous times. |
You are aware that you got to wait for workflow run events from the GitHub webhook before the metrics are getting displayed, right? |
Hi Everyone,
I have not been able to get workflow metrics no matter what I tried. I have been getting this error.
level=error ts=2023-10-26T15:34:42.365656874Z msg="failed to store github event" type=workflow_run error="failed to find record: sql: expected 15 destination arguments in Scan, not 1" 2023/10/26 15:34:42 http: superfluous response.WriteHeader call from github.com/promhippie/github_exporter/pkg/action.handler.func2.1 (server.go:289)
and then
level=error ts=2023-10-26T15:34:50.889038215Z collector=workflow msg="Failed to fetch workflows" err="sql: Scan error on column index 0, name \"owner\": destination not a pointer"
I use kubernetes
The text was updated successfully, but these errors were encountered: