Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork849
Stuck on "Fetching closed dates for issues"#965
-
Hey guys I have 2 repos, front end and backend. Front end works fine when i generate changelog for the first time, however backend stucks here:
Then it just stuck for more than a day now, i tried to cancel, rerun, run from docker, nothing works. Any idea why? When I cancel with My |
BetaWas this translation helpful?Give feedback.
All reactions
Replies: 22 comments 19 replies
-
Hi, (Go for hello everyone, we want to includeeveryone!) Thanks for the report! Can you add a backtrace of where you Ctrl-c? That may or may not make this easier to pinpoint. |
BetaWas this translation helpful?Give feedback.
All reactions
👍 1
-
Hey guys, gee you're fast in replying! Thanks for the amazing project Here's Also if its worth noting, this project is in laravel (php) if that affects anything which i think it shouldn't? The other one that works is in react Here's the full log after Ctrl - c
|
BetaWas this translation helpful?Give feedback.
All reactions
-
|
BetaWas this translation helpful?Give feedback.
All reactions
-
I tried ruby 3.1.2 with github-changelog-generator 1.16.4, still stucks |
BetaWas this translation helpful?Give feedback.
All reactions
-
Hey, i tried running with ruby 2.7 Same result after 20 minutes that I have to cancel it
|
BetaWas this translation helpful?Give feedback.
All reactions
-
Thanks for making an attempt! |
BetaWas this translation helpful?Give feedback.
All reactions
-
|
BetaWas this translation helpful?Give feedback.
All reactions
-
No i didn't get anything at all,
|
BetaWas this translation helpful?Give feedback.
All reactions
👍 1😕 2
-
What if you leave off the initial && just after the "debug" word? |
BetaWas this translation helpful?Give feedback.
All reactions
👍 1
-
Oh, yeah, totally missed that. It should be |
BetaWas this translation helpful?Give feedback.
All reactions
-
Omg guys i missed it!! Here's the log. although not sure if it meant something. It stucked at the same stream after 2.6s
|
BetaWas this translation helpful?Give feedback.
All reactions
-
This log file looks okay. |
BetaWas this translation helpful?Give feedback.
All reactions
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
-
I got same issue now. But in my case, it also shows a warning about 2 weeks ago, the same script works well. But for now, it start stuck ================================ I just find that |
BetaWas this translation helpful?Give feedback.
All reactions
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
-
So I'm running to this exact issue, and I tried to downgrade back to the original version I was using (
I tried to uninstall and reinstall, but still the same thing:
How do I cleanly uninstall everything and try again? Other notes: EDIT: I just tried to uninstall every single Ruby gem that this library installed, and then reinstall |
BetaWas this translation helpful?Give feedback.
All reactions
-
Weirdly it only happens in some repo. In my case only 1 repo, the rest are fine.. |
BetaWas this translation helpful?Give feedback.
All reactions
-
Can you share their specific github_changelog_generator invocations, so I can try and reproduce? |
BetaWas this translation helpful?Give feedback.
All reactions
-
Hey I just manage to try it again, after I downgraded to |
BetaWas this translation helpful?Give feedback.
All reactions
-
So, the new feature in 1.16 and later is a much-more-efficient asynchronous way of talking to GitHub - and we're interested in having that tested out, with combinations that consistently get stuck, so that we can analyze what is going wrong. |
BetaWas this translation helpful?Give feedback.
All reactions
-
It looks like you might be using a mixed up install. I see in the log the executable is coming from your system. Make sure you install it using bundler and then use |
BetaWas this translation helpful?Give feedback.
All reactions
-
@ioquatix Most users of this tool are not primarily Ruby users Here's a very small guide to what the above meant. Using Bundler & |
BetaWas this translation helpful?Give feedback.
All reactions
👍 1
-
Thanks@olleolleolle . I'm new to Ruby &
After that, everything worked as expected! |
BetaWas this translation helpful?Give feedback.
All reactions
Uh oh!
There was an error while loading.Please reload this page.
-
BetaWas this translation helpful?Give feedback.
All reactions
-
Hello, and welcome to a threaded discussion about this! |
BetaWas this translation helpful?Give feedback.
All reactions
👍 1
-
Not sure why everyone, but after downgrading to |
BetaWas this translation helpful?Give feedback.
All reactions
👍 1
-
Can you add me to the repo which has the problem. Otherwise I cannot test. |
BetaWas this translation helpful?Give feedback.
All reactions
-
It's a company private repo unfortunately.. Sorry |
BetaWas this translation helpful?Give feedback.
All reactions
👍 1
-
Okay, if you prefer, you can pay me as a consultant and I will fix your problem :) I am happy to sign a contract/NDA. |
BetaWas this translation helpful?Give feedback.
All reactions
-
Hello there, I am testing github-changelog-generator on a new repo and I am getting the same error discussed here: it gets stuck when fetching closed dates for issues. My repo ishttps://github.com/kong/kong/ , it is open source. In my case I am using the docker image to attempt to generate the changelog. I have tried several combinations of options, all get stuck. Here a simple one:
It finds the tags,
It receives the issues around the 2-minute mark:
Then the logs stop at around the 4-min mark. Last lines:
|
BetaWas this translation helpful?Give feedback.
All reactions
👍 1
-
@kikito 👋 How does v1.16.4 work for your use-case? |
BetaWas this translation helpful?Give feedback.
All reactions
-
Hi, nice turnaround! I have tried again (with Docker) and got the same result (stuck after It seems that dependabot has not yet pushed the v1.16.4 bump tohttps://github.com/github-changelog-generator/docker-github-changelog-generator/pulls . For now I am stuck to trying this with Docker, so I will have to wait until v1.16.4 lands there. |
BetaWas this translation helpful?Give feedback.
All reactions
-
Right, there were a few levers to pull, there, and soon, the version ought to be more ready to go out. |
BetaWas this translation helpful?Give feedback.
All reactions
-
Hello, since I saw that 1.16.4 was already bumped in the docker image, I tried manually creating the image myself:
And then used it to try to generate the changelog:
Unfortunately that also didn't work. It found and fetched the tags
Unfortunately it failed, again at the 4 minute mark. The failure might be more useful than the previous one since it includes a traceback:
I'm under the impression that the generator is just trying to pull too much stuff from Github, and at some point I get rate-limited, and the changelog dies (it would be nice it if died with a more specific error). I am ok with doing more tests like this. But is there a way to limit the amount of info the generator pulls from github? Currently I am not interested in generating the whole changelog from scratch, just the "Unreleased" changes. Can this be used somehow to limit the amount of issues pulled from github? They should be a substantial subset of the whole list. |
BetaWas this translation helpful?Give feedback.
All reactions
-
Update: tried again, same command as before:
That was ~40 minutes ago. The generator is still "working on it" .. kindof. Here's the latest logs:
|
BetaWas this translation helpful?Give feedback.
All reactions
-
I can confirm this issue persists in the latest 1.16.4. - no matter what type of flags I add to the gem command, it gets stuck on |
BetaWas this translation helpful?Give feedback.
All reactions
-
A good workaround is to use I have a complicated bash + awk script that concatenates two CHANGELOG.md files, such that you can fetch only the most recent stuff and whack it on the end. The reason I wanted this originally is so that I can avoid the "summary issue" system, and simply edit the changelog in-place to add commentary. A nice side effect is that I am not affected by the hang. |
BetaWas this translation helpful?Give feedback.
All reactions
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
-
We discovered the same problem. There is a very easy reproduction. Basically exclude all tags present in the repository. Something like Will try to work around that with placing some dummy tags and report back soonish :) |
BetaWas this translation helpful?Give feedback.
All reactions
-
things are getting weirder. The only way I can generate a changelog with excluding almost all tags is allowing at least one tag. It has to be somewhere in the middle of the history though. If I allow a very early or a very recent tag the process also hangs at |
BetaWas this translation helpful?Give feedback.
All reactions
-
also memory usage is slowly creeping up if the process is kept running |
BetaWas this translation helpful?Give feedback.
All reactions
This discussion was converted from issue #961 on May 19, 2021 07:05.