waka-readme-stats: BUG : Action Fails

Describe the bug

Actions get failed from a month…

Traceback (most recent call last):
  File "/waka-readme-stats/main.py", line 221, in <module>
    run(main())
  File "/usr/local/lib/python3.11/asyncio/runners.py", line 190, in run
    return runner.run(main)
           ^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/asyncio/runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/asyncio/base_events.py", line 653, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/waka-readme-stats/main.py", line 208, in main
    stats = await get_stats()
            ^^^^^^^^^^^^^^^^^
  File "/waka-readme-stats/main.py", line 156, in get_stats
    yearly_data, commit_data = await calculate_commit_data(repositories)
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/waka-readme-stats/yearly_commit_calculator.py", line [37](https://github.com/ddok2/ddok2/actions/runs/4403414537/jobs/7711737364#step:3:38), in calculate_commit_data
    await update_data_with_commit_stats(repo, yearly_data, date_data)
  File "/waka-readme-stats/yearly_commit_calculator.py", line 65, in update_data_with_commit_stats
    date = search(r"\d+-\d+-\d+", commit["committedDate"]).group()
                                  ~~~~~~^^^^^^^^^^^^^^^^^
TypeError: 'NoneType' object is not subscriptable
sys:1: RuntimeWarning: coroutine 'AsyncClient.get' was never awaited

Github repository link

About this issue

Original URL
State: open
Created a year ago
Reactions: 11
Comments: 38 (1 by maintainers)

Commits related to this issue

Apply feedback cf) https://github.com/anmol098/waka-readme-stats/issues/425#issuecomment-1497159015 — committed to ddok2/ddok2 by ddok2 a year ago

Most upvoted comments

@ddok2, could you please inspect, how does it happen that committedDate is None? According to GitHub documentation, it’s a required field. If it becomes None sometimes, we can use the None check you propose, and I would suggest writing to GitHub support about the issue. Because in general in my opinion we would rather rely on documentation then doublecheck everything.

pseusys on Apr 30, 2023

@willnaoosmith, there’s no such option yet, but we are always open to ideas and/or proposals!

pseusys on May 9, 2023

I think the problem is that once the repository has enough commits, it takes too long for GitHub to process the data, so it returns an 503 error. Re-doing the repository, cleaning the commit history might do it. Mine has 2.720 commits as now. @mikebronner has 1K. So it might be a new limitation on the GitHub API, or something like this. If anyone tries to fix it by doing my suggestion, let us know!

I think we fhould file an issue to GitHub support, shouldn’t we?

Yup both would be good. Once I got some time, I’m going to try what I suppose might work, just to get some intel on the cause of the problem and help a little!

willnaoosmith on May 4, 2023

@pseusys, I agree with your comment. I’ll inspect the issue again. If this is a problem with Gtihub, I will open an issue with Github support and close this issue.

ddok2 on May 1, 2023

@doctormin I used all flag your settings, and it worked. Thank you

eby8zevin on Apr 5, 2023

In my case, time-out errors happened when fetching the commit history of a large repo of mine So this bug can be temporarily avoided by turning:

SHOW_COMMIT flag to "False" in your GitHub Action YML file

You guys can give it a try: example

doctormin on Apr 5, 2023