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

Build 161009 Stable causes git errors #896

Closed
alexjking opened this issue Oct 10, 2016 · 14 comments
Closed

Build 161009 Stable causes git errors #896

alexjking opened this issue Oct 10, 2016 · 14 comments
Labels

Comments

@alexjking
Copy link

@alexjking alexjking commented Oct 10, 2016

Versions

ConEmu build: 161009 x32/x64
OS version: Windows 7 Enterprise x64
git-bash

Problem description

The latest update causes the error error: failed to push some refs to 'git@...' when running git push. The push is successful however this error displays despite the push being successful.

Steps to reproduce

  1. Open ConEmu 161009 [64]
  2. Open git bash
  3. Change to a git directory
  4. git push

Actual results

`error: failed to push some refs to 'git@...', however git pushes anyway

Performing git push from git bash by itself (without ConEmu) doesn't display the error so it seems that ConEmu is causing this problem.

Expected results

There should be no error messsage.

@Maximus5
Copy link
Owner

@Maximus5 Maximus5 commented Oct 10, 2016

  1. You said "161009", but it's not clear if the error appears in that build or existed before? Try previous ConEmu build.
  2. The phrase "open git bash" is undistinguished. What do you run exactly?

Third-party application problems

@CendaL
Copy link

@CendaL CendaL commented Oct 10, 2016

I have similar problem with PowerShell module posh-git.

Commands git stash and git stash pop do nothing. There is not output and files are not stashed. Please see the screenshot where I first run commands in ConEmu and then directly in Powershell console:
conemubug

The previous version worked fine.

Edited: update screenshot to show status bar.

@Maximus5
Copy link
Owner

@Maximus5 Maximus5 commented Oct 10, 2016

it's not clear if the error appears in that build or existed before? Try previous ConEmu build.

@CendaL
Copy link

@CendaL CendaL commented Oct 10, 2016

Adding screenshot from previous version (161002x64):
conemubug2

Please let me know if you need some logs.

Edited: update screenshot to show status bar.

@Maximus5 Maximus5 added the hooks label Oct 10, 2016
@lhecker
Copy link

@lhecker lhecker commented Oct 10, 2016

@Maximus5 Sorry to chime in like this, but my issues with 161009 are even worse and I believe they are related to this issue:

I'm using MSYS2 and if I start a bash shell now it will only print bash-4.3$ in black and white, while it used to print user@host MSYS /c/Users/user (colorized). Running e.g. pacman fails with error: GPGME error: Invalid crypto engine and many other tools show subtile issues like the above with git.

If you disable Inject ConEmuHk it works though, so I guess that's what's causing it.

@alexjking
Copy link
Author

@alexjking alexjking commented Oct 10, 2016

@Maximus5 This problem occurs in build 161009 when using the {Bash::Git bash} predefined task "%ConEmuDir%\..\Git\git-cmd.exe" --no-cd --command=usr/bin/bash.exe -l -i. I get the git error error: failed to push some refs to ....... when running git push.

I've checked the previous build 161002 and can't reproduce the problem there. Let me know if I can give you further information.

@mramato
Copy link

@mramato mramato commented Oct 10, 2016

I'm also seeing this problem and will happily supply any desired information to help debug it.

@damtur
Copy link

@damtur damtur commented Oct 10, 2016

It also screwed up Windows GitBash branch displaying. Please rollback stable version to previous one as this is making ConEmu unusable.

@Maximus5
Copy link
Owner

@Maximus5 Maximus5 commented Oct 10, 2016

161009a

@ghost
Copy link

@ghost ghost commented Oct 10, 2016

@Maximus5 Thanks this fixed my issues. #905

@mikeyw
Copy link

@mikeyw mikeyw commented Oct 11, 2016

@Maximus5 thank you!

@mramato
Copy link

@mramato mramato commented Oct 11, 2016

@Maximus5 I can confirm it's fixed as well. Thanks for the quick turnaround!

@dig412
Copy link

@dig412 dig412 commented Oct 13, 2016

@Maximus5 Thanks for the quick fix on this - your dedication to this program is incredibly impressive!

@alexjking
Copy link
Author

@alexjking alexjking commented Oct 13, 2016

@alexjking alexjking closed this Oct 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
8 participants
You can’t perform that action at this time.