-
Notifications
You must be signed in to change notification settings - Fork 348
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
[BUG]: stuck on Generating the commit message #259
Comments
Hi, just to confirm I'm having the same problem as @zhiyue and @FrancoLab |
will get to it soon, thanks for creating the ticket! |
has this been resolved? |
Same issue here. Please let me know if this has been resolved. |
I have the same issue, reinstall didn'help. Strange thing is that it worked fine and started to hang without making any changes in the system or config. Node 20.9.0, Windows 10 |
Not yet resolved guys, if anyone have time to look into it — much appreciated <3 |
@di-sukharev I made some tests and this is what I came up with:
Unfortunatelly I don't have time to debug this deeper and implement fix but I think it would be good to have simply a check that |
Stale issue message |
reopening, will take a look at this |
Same problem here using Claude 3.5 Sonnet! What is even more strange is that when I log on Anthropic console, it does not show OpenCommit has made a call at all! Also maybe the issue is I deleted bunch of useless files from my repo and the OCO is trying to feed it into the Claude? Edit: I think yeah feeding CSV in there is a problem
|
I've had this issue in the past then it somehow resolved and now all of a sudden I'm having it again. My main problem with it is getting left out in the blue without an error message or being able to enable some verbose flag that might give me some insight of what's going on. Just stuck. |
Opencommit Version
3.0.3
Node Version
v18.7.0
NPM Version
9.8.1
What OS are you seeing the problem on?
Other Linux Distro
What happened?
stuck on

Expected Behavior
normal output
Current Behavior
stuck
Possible Solution
No response
Steps to Reproduce
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: