-
Notifications
You must be signed in to change notification settings - Fork 41
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
Action fails when too many jobs trying to track different repos in the same data repo #11
Comments
@jgehrcke Let me know if I can help more than just reporting this. It would be great to fix all of this, to use this tool more extensively, as I am planning to grow the number of repos from 34 to more over time. It is the most valuable tool, I could find for tracking repo development over time. Thank you again! |
I could not quite make sense of this one. Both,
I am adding a patch that changes the way the DatetimeIndex is translated to a tz-aware object, which hopefully addresses this problem. It's a little disappointing to not understand it precisely. |
That somewhat suggests that df_clones and df_views looked rather differently structurally than what's expected. Update: empty index explains that error msg:
|
Could it be that this token was actually truncated and/or maybe this is related to one of your code changes? I notice
When things work as expected, that should be the log pattern:
It's likely that the error message |
See issue #11. This explicit index construction will create a tz-aware DatetimeIndex even if the data is empty: >>> pd.DatetimeIndex(data=[], tz="UTC") DatetimeIndex([], dtype='datetime64[ns, UTC]', freq=None)
Something fishy went on in the context of what was reported in #11.
@ChameleonTartu would you mind retrying things with the current head of main? I think I've addressed all issued reported to date (maybe have a look at the changelog). Happy to cut a release, but ideally only after getting your confirmation that things indeed work. |
@jgehrcke I made a run: https://github.com/ChameleonTartu/buymeacoffee-repo-stats/actions/runs/748508227 The only use-case that doesn't work is:
And all jobs failed with the same message: https://github.com/ChameleonTartu/buymeacoffee-repo-stats/runs/2343584927?check_suite_focus=true I suspect that repos may have been created a long time ago, so they have different API token formats, can it be the cause? Any idea? |
OK, you're workflow file is bad in a subtle way! Mean trap: https://github.com/ChameleonTartu/buymeacoffee-repo-stats/blob/b6d089f2bc01462e05fe8100ce1f27cfd3a24909/.github/workflows/stats.yml#L138 @ChameleonTartu you have |
@jgehrcke Thank you! I didn't notice these nuances. I auto-generated some of the jobs, so it looks like I got some of them wrong. Cool-cool-cool! |
@ChameleonTartu ok : ) Please leave feedback again when the current head of main worked for all your jobs : ) |
@jgehrcke Everything works smoothly: https://github.com/ChameleonTartu/buymeacoffee-repo-stats/actions/runs/748788117 Amazing! |
This project looks amazing!
My idea was to track all public repos and analyze them once in a while. It looks like when I have too many jobs running, the action fails. For instance, when one job is pushed before another one. My GitHub repo.
Also, there is another issue with amazon-mws-subscriptions-maven:
Another data frame issue:
Git clone issue:
All other issues are the same as those mentioned.
The text was updated successfully, but these errors were encountered: