Stuck on "Fetching closed dates for issues" #965
Replies: 22 comments 19 replies
-
Hi, (Go for hello everyone, we want to include everyone!) Thanks for the report! Can you add a backtrace of where you Ctrl-c? That may or may not make this easier to pinpoint. |
Beta Was this translation helpful? Give feedback.
-
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
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Hey, i tried running with ruby 2.7 Same result after 20 minutes that I have to cancel it
|
Beta Was this translation helpful? Give feedback.
-
Thanks for making an attempt! |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
No i didn't get anything at all,
|
Beta Was this translation helpful? Give feedback.
-
What if you leave off the initial && just after the "debug" word? |
Beta Was this translation helpful? Give feedback.
-
Oh, yeah, totally missed that. It should be |
Beta Was this translation helpful? Give feedback.
-
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
|
Beta Was this translation helpful? Give feedback.
-
This log file looks okay. |
Beta Was this translation helpful? Give feedback.
-
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 |
Beta Was this translation helpful? Give feedback.
-
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 |
Beta Was this translation helpful? Give feedback.
-
Weirdly it only happens in some repo. In my case only 1 repo, the rest are fine.. |
Beta Was this translation helpful? Give feedback.
-
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 |
Beta Was this translation helpful? Give feedback.
-
@ioquatix Most users of this tool are not primarily Ruby users Here's a very small guide to what the above meant. Using Bundler &
|
Beta Was this translation helpful? Give feedback.
-
Thanks @olleolleolle . I'm new to Ruby &
After that, everything worked as expected! |
Beta Was this translation helpful? Give feedback.
-
Not sure why everyone, but after downgrading to |
Beta Was this translation helpful? Give feedback.
-
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 is https://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:
|
Beta Was this translation helpful? Give feedback.
-
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 |
Beta Was this translation helpful? Give feedback.
-
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 :) |
Beta Was this translation helpful? Give feedback.
-
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
ctrl + c
it just says interrupt, 'block in make_fiber`. not sure what's that...My
github_changelog_generator
version is:1.16.2
Ruby version:
ruby 3.0.0p0 (2020-12-25 revision 95aff21468) [x86_64-darwin20]
Gem version:
3.2.3
Beta Was this translation helpful? Give feedback.
All reactions