Generate commit message is not working as expected

[w3llcod3]

Hello,

Thanks for the great product Codeim. I've been using it for a while and it's great. However, I'm facing an issue related to generating commit messages as it's not working.

Upon clicking "Generate commit message", I get the following error

Unable to generate commit message: ConnectError: [unknown] file not found

[salewise-dev]

I'm facing the same issue as well

[charlwillia6]

I have received this message from day one. This has never worked for me.

[lizardwine]

same issue

[mriostamez]

Same issue for me in Cursor.

[scho-to]

I got it working once, but I removed codeium in the meantime..

Now with the new Pro Plan, i am back an trying to get it working again.

Here is my workaround for now:
Just output the git diff in the terminal and use the @Terminal:all content with the prompt:
"Generate a conventional git message based on the given output and summarize changes for future readers."

You might have to clear the terminal before using this workaround.

The @Diff command is not working at all for me..

[vinshield]

Same issue for me

[vscodesyncsettings]

Same issue here too

[arman-async]

This is my problem

[GustavoBitten]

Same here

[chengazhen]

same here

[PytatoDuck]

Same here, I get this Error in the Terminal Output.

E1017 03:29:52.087525  6712 rpcs_commit_messages.go:76] Failed to generate commit message: error grabbing LLM response: stream error

[dwichers]

I have the same issue in Cursor but without the File not found error.

[etmmafl]

I got it working once, but I removed codeium in the meantime..

Now with the new Pro Plan, i am back an trying to get it working again.

Here is my workaround for now: Just output the git diff in the terminal and use the @Terminal:all content with the prompt: "Generate a conventional git message based on the given output and summarize changes for future readers."

You might have to clear the terminal before using this workaround.

The @Diff command is not working at all for me..

this worked actually very well. In my case I had to use git status for it to work.

[Mohamed3nan]

It seems the generated text isn't being pasted into the commit input, even though it was created successfully!
I1028 16:49:20.734349 7592 commit_messages.go:128] Generating commit message took 1.3907165s

[PytatoDuck]

It seems the generated text isn't being pasted into the commit input, even though it was created successfully! I1028 16:49:20.734349 7592 commit_messages.go:128] Generating commit message took 1.3907165s

🤔 I get a different error, can't grab the response.

E1028 19:17:07.134789 14472 rpcs_commit_messages.go:76] Failed to generate commit message: error grabbing LLM response: stream error

[Saket6198]

still having the same issue, any updates? @dwichers

[dwichers]

still having the same issue, any updates? @dwichers

Still not working :/
I'm using Commit Message Editor
https://marketplace.visualstudio.com/items?itemName=adam-bender.commit-message-editor

With a slightly custommized template to adhere to the Conventional Commits
https://www.conventionalcommits.org/en/v1.0.0/

[20240816]

In the meantime I'm using GPT Commit Generator which, after providing an OpenAI API key and a customizable prompt, involves clicking only once on the new 'Generate Commit' button per commit.
Let us know when Codeium eventually has this fixed please!

In my case the VS Code error generated by Codeium is:

E1105 16:50:06.630669 4751 rpcs_commit_messages.go:76] Failed to generate commit message: error grabbing LLM response: stream error

[vscodesyncsettings]

I have the same issue in Codeium. Here is the workaround I use:

1. Make changes in my files and stage them

2. Run git diff --staged in the terminal
   

3. In Codeium chat, type @Terminal, Select "Last terminal command" andtype "Generate commit message".
   

[ngocdd]

+1 on 09 Nov 2024

[llama-for3ver]

I have the same issue in Codeium. Here is the workaround I use:

1. Make changes in my files and stage them

2. Run `git diff --staged` in the terminal
   ![image](https://private-user-images.githubusercontent.com/114229500/383132313-d2a07ced-9741-4423-801f-fece9f5ed6ec.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzEyMjU0NDQsIm5iZiI6MTczMTIyNTE0NCwicGF0aCI6Ii8xMTQyMjk1MDAvMzgzMTMyMzEzLWQyYTA3Y2VkLTk3NDEtNDQyMy04MDFmLWZlY2U5ZjVlZDZlYy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQxMTEwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MTExMFQwNzUyMjRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT03ODJiZWYzMDYyYjc0ZmMxYjg5YzE0MGEwNDVhNjRlMWNhYjk5YWEzNzM3ZjFiNTNiYzA3ZjcxM2Y3ZDNjODhiJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.Enx-VlO1X9fB8aifk1VAaLuN_UMyQ8OU6lB6C0Pg16Y)

3. In Codeium chat, type @Terminal, Select "Last terminal command" andtype "Generate commit message".
   ![image](https://private-user-images.githubusercontent.com/114229500/383132506-c0a360d7-a87b-4bba-9b06-73df397a1e0f.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzEyMjU0NDQsIm5iZiI6MTczMTIyNTE0NCwicGF0aCI6Ii8xMTQyMjk1MDAvMzgzMTMyNTA2LWMwYTM2MGQ3LWE4N2ItNGJiYS05YjA2LTczZGYzOTdhMWUwZi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQxMTEwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MTExMFQwNzUyMjRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0zYmRhYjUxNWI2MzIwNDY4YmUwYTgyMzQxYzNhODRiMzk2ODljYTE1ZDhiZTg3NWU2YTU3ZjI0OGVjODg2MWFjJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.mu6WBljBm7IX-Wr4Ymm8F9sQmjy9Fp61EhJTu5eGbow)

Unless I'm doing something wrong, git diff brings up an interactive window which doesn't seem to work properly with Codeium. Piping it into cat seems to work better

[Mark3xtrm]

No update on this?

[nnatchunn]

I have the same issue in Codeium. Here is the workaround I use:

1. Make changes in my files and stage them

2. Run `git diff --staged` in the terminal
   ![image](https://private-user-images.githubusercontent.com/114229500/383132313-d2a07ced-9741-4423-801f-fece9f5ed6ec.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzEyMjU0NDQsIm5iZiI6MTczMTIyNTE0NCwicGF0aCI6Ii8xMTQyMjk1MDAvMzgzMTMyMzEzLWQyYTA3Y2VkLTk3NDEtNDQyMy04MDFmLWZlY2U5ZjVlZDZlYy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQxMTEwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MTExMFQwNzUyMjRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT03ODJiZWYzMDYyYjc0ZmMxYjg5YzE0MGEwNDVhNjRlMWNhYjk5YWEzNzM3ZjFiNTNiYzA3ZjcxM2Y3ZDNjODhiJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.Enx-VlO1X9fB8aifk1VAaLuN_UMyQ8OU6lB6C0Pg16Y)

3. In Codeium chat, type @Terminal, Select "Last terminal command" andtype "Generate commit message".
   ![image](https://private-user-images.githubusercontent.com/114229500/383132506-c0a360d7-a87b-4bba-9b06-73df397a1e0f.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzEyMjU0NDQsIm5iZiI6MTczMTIyNTE0NCwicGF0aCI6Ii8xMTQyMjk1MDAvMzgzMTMyNTA2LWMwYTM2MGQ3LWE4N2ItNGJiYS05YjA2LTczZGYzOTdhMWUwZi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQxMTEwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MTExMFQwNzUyMjRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0zYmRhYjUxNWI2MzIwNDY4YmUwYTgyMzQxYzNhODRiMzk2ODljYTE1ZDhiZTg3NWU2YTU3ZjI0OGVjODg2MWFjJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.mu6WBljBm7IX-Wr4Ymm8F9sQmjy9Fp61EhJTu5eGbow)

Unless I'm doing something wrong, git diff brings up an interactive window which doesn't seem to work properly with Codeium. Piping it into cat seems to work better

In that case, you might need to use the --no-pager flag before using the diff command.

git --no-pager diff --staged

[llama-for3ver]

That’s it - I knew there was an argument for it, but I couldn’t find it 😅

…

On Tue, Nov 12, 2024 at 06:51, Nattakan Chuntra ***@***.***(mailto:On Tue, Nov 12, 2024 at 06:51, Nattakan Chuntra <<a href=)> wrote: >> I have the same issue in Codeium. Here is the workaround I use: >> >> 1. Make changes in my files and stage them >> >> 2. Run `git diff --staged` in the terminal >>  >> >> 3. In Codeium chat, type @Terminal, Select "Last terminal command" andtype "Generate commit message". >>  > > Unless I'm doing something wrong, git diff brings up an interactive window which doesn't seem to work properly with Codeium. Piping it into cat seems to work better In that case, you might need to use the --no-pager flag before using the diff command. git --no-pager diff --staged — Reply to this email directly, [view it on GitHub](#83 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AKQRM7EA4TRN24BCB34IHJ32ADVCVAVCNFSM6AAAAABNFKYCTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRYG4ZTAMBWGQ). You are receiving this because you commented.Message ID: ***@***.***>

[web-sujal]

Getting this error when trying to generate commit message.

[JanbertCampos]

same problem this is trash

[Mohamed-Elrayes]

Same problem , No update on this?

[axellpadilla]

It "completed", but didn't write it to the field, nor even using the file version of commit message:

Also, it doesn't copy it to the clipboard (that could be an easy workaround).

[HiChen404]

Same problem.

[ItsBenDov]

Same problem

[skittonik]

Same problem.

[paulinofonsecas]

Same problem

[DIHE-GitHub]

Same problem

[vadimmelnicuk]

Same problem as @axellpadilla