Skip to content
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

"No commit messages were generated" #35

Closed
1 task
caiguo37 opened this issue May 19, 2024 · 5 comments
Closed
1 task

"No commit messages were generated" #35

caiguo37 opened this issue May 19, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@caiguo37
Copy link

Bug description

I'm using the local model (ollama with codellama) to generate a commit. It works sometimes and fails sometimes with the warning information: "⚠ No commit messages were generated."
截屏2024-05-19 11 33 49

And if I enable OLLAMA_STREAM, after streaming for a while, a new error message is displayed: Failed to extract messages from response.
截屏2024-05-19 11 35 32

aicommit2 version

1.8.6

Environment

System:
    OS: macOS 14.4.1
    CPU: (10) arm64 Apple M2 Pro
    Memory: 252.88 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 21.5.0 - ~/.asdf/installs/nodejs/21.5.0/bin/node
    npm: 10.2.4 - ~/.asdf/plugins/nodejs/shims/npm
    pnpm: 9.0.4 - ~/.asdf/shims/pnpm

Can you contribute a fix?

  • I’m interested in opening a pull request for this issue.
@caiguo37 caiguo37 added the bug Something isn't working label May 19, 2024
@tak-bro
Copy link
Owner

tak-bro commented May 19, 2024

Thank you for your interest. There seems to be a problem with parsing messages. I'll fix it as soon as possible

@tak-bro
Copy link
Owner

tak-bro commented May 24, 2024

@caiguo37 I fine-tuned the prompt, but sometimes AI doesn't return the correct commit message.
I added the logging option to see the full response message. It support from v1.9.0.

You can set it up with the command below.
aicommit2 config set logging=true

@caiguo37
Copy link
Author

截屏2024-05-24 13 59 38

Didn't see any log generated.

@caiguo37
Copy link
Author

success.log
fail.log
fail2.log
success2.log

Using the same content, logs of failure and success. Took a glance, didn't find any difference.

@tak-bro
Copy link
Owner

tak-bro commented May 24, 2024

Thank you for sharing the error log.
I checked and found that the fail case is not correct format of a conventional commit message.
In the case of fail.log, the type is git, but it is not an conventional commit type.
The message in fail2.log is not in the form of type(scope): description.

(I left a comment on another account, so I wrote again.)

@tak-bro tak-bro closed this as completed May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants