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

Committing fails: could not read log file, Invalid argument #3800

Closed
patrikturi opened this issue Jul 1, 2017 · 13 comments
Closed

Committing fails: could not read log file, Invalid argument #3800

patrikturi opened this issue Jul 1, 2017 · 13 comments

Comments

@patrikturi
Copy link

patrikturi commented Jul 1, 2017

Do you want to request a feature or report a bug?
bug
What is the current behavior?
When I try to commit, I get the following error message:

"git" commit -F "C:\Users\p\Documents\projects\teamplay\.git\COMMITMESSAGE"
fatal: could not read log file 'C:\Users\p\Documents\projects\teamplay\.git\COMMITMESSAGE"': Invalid argument

(notice the missing " on the left side of the error message)
If I execute exactly the same git commit command in Git Bash, it creates the commit just fine.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.

  1. In a repository add a file or make change
  2. Open the Commit dialog
  3. Stage files (staging works fine)
  4. Write a commit message
  5. Click Commit

What is the expected behavior?
A successful commit.
Which versions of GitExtensions, GIT and Windows are affected by this issue? Did this work in previous versions of our tool?
GitExtensions 2.50.00 on Windows 10

@Tinsus
Copy link

Tinsus commented Jul 2, 2017

since the last update to 2.50.00 I have this same error. Currently GitExtensions is useless for me.

@dogancelik
Copy link
Contributor

Same error here, 2.50 final

@jbialobr
Copy link
Member

jbialobr commented Jul 3, 2017

What is the content of the C:\Users\p\Documents\projects\teamplay.git file?

@patrikturi
Copy link
Author

patrikturi commented Jul 3, 2017

sorry it is projects\teamplay\.git it's just the markdown removing one \
The COMMITMESSAGE file is there with the correct message.

@jbialobr
Copy link
Member

jbialobr commented Jul 4, 2017

Can you disable ConEmu and see if the problem still occurs?

@pysco68
Copy link

pysco68 commented Jul 4, 2017

Hi there,

I just ran into the same issue, disabling ConEmu as @jbialobr suggested fixed the issue.

NOTE: if you need additional debugging info just tell me what to try.

@patrikturi
Copy link
Author

Disabling ConEmu works for me too. Thank you.

@jbialobr jbialobr added this to the ConEmu-KnownIssues milestone Jul 7, 2017
@VsevolodGolovanov
Copy link

I use 2.50.01 on 2 PCs (both Win7). On one commit works fine, but on the other this issue happens consistently:

"git" commit -F "F:\rep\TechService-3.20\.git\COMMITMESSAGE"
fatal: could not read log file 'F:\rep\TechService-3.20\.git\COMMITMESSAGE"': Invalid argument
Done

@bastianeicher
Copy link
Contributor

Also encountered this with Git Extensions 2.50.01 on multiple Windows 10 machines. Disabling ConEmu also "fixes" the issue for me.

@Bikeman868
Copy link

Can someone add instructions on how to "disable ConEmu" I have no idea what this is.

@bastianeicher
Copy link
Contributor

@Bikeman868: Take a look at the link @jbialobr posted above:
https://git-extensions-documentation.readthedocs.io/en/latest/settings.html#advanced-general-use-console-emulator-for-console-output-in-command-dialogs

jbialobr added a commit that referenced this issue Sep 5, 2017
…3800.

Run scripts through the standard Process instead of conemu-inside - even if configured to use conemu.
Conemu-inside has a complex arguments parsing logic which is not able to handle correctly quoted parameters.
Fixes #3691.
@jbialobr jbialobr modified the milestones: 2.50.02, ConEmu-KnownIssues Sep 5, 2017
@jbialobr jbialobr closed this as completed Sep 5, 2017
jbialobr added a commit that referenced this issue Sep 5, 2017
…3800.

Run scripts through the standard Process instead of conemu-inside - even if configured to use conemu.
Conemu-inside has a complex arguments parsing logic which is not able to handle correctly quoted parameters.
Fixes #3691.

(cherry picked from commit b304969)
@givanse
Copy link

givanse commented May 30, 2018

Has the linked page been updated or changed? I look at the text in there and have no idea what to do with the info there. How do you disable ConEmu?

@RussKie
Copy link
Member

RussKie commented May 30, 2018

No the link above is still pointing to the correct location.

Here's how to find settings:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants