Unhandled Exception on Windows 7 #12

shahabganji · 2018-10-16T04:58:46Z

I have installed the tool via this command dotnet tool install git-istage -g and I get the following error when running the git istage command, or git istage .:

Unhandled Exception: System.IO.IOException: The handle is invalid
   at System.ConsolePal.get_CursorVisible()
   at GitIStage.Application.Run() in /home/vsts/work/1/s/src/git-istage/Application.cs:line 33
   at GitIStage.Program.Main() in /home/vsts/work/1/s/src/git-istage/Program.cs:line 32

I just created a folder and within that, I have created a new git repository by caling git init, then added a simple txt file and add Hello World text inside that. then I ran git istage . and I get the above mentioned error.

worth to note that I am running Windows 7

and here is my dotnet --info output

.NET Core SDK (reflecting any global.json):
 Version:   2.1.403
 Commit:    04e15494b6

Runtime Environment:
 OS Name:     Windows
 OS Version:  6.1.7601
 OS Platform: Windows
 RID:         win7-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.1.403\

Host (useful for support):
  Version: 2.1.5
  Commit:  290303f510

.NET Core SDKs installed:
  2.1.402 [C:\Program Files\dotnet\sdk]
  2.1.403 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

The text was updated successfully, but these errors were encountered:

drewnoakes · 2018-10-16T09:04:11Z

What terminal/console program are you using?

shahabganji · 2018-10-16T09:39:17Z

@drewnoakes

I am using Git Bash (MINGW64) on Windows 7.

This might be helpful to know when using git bash as VS Code's terminal it has no problem, but when i open the bash from explorer on my git repository folder it fails with the exception.

drewnoakes · 2018-10-16T14:19:47Z

Sounds like #9. Does it work in cmd.exe?

shahabganji · 2018-10-16T15:01:19Z

That works with cmd.exe it also works with git bash as VS Code's internal terminal.

jvlppm · 2018-10-17T13:10:58Z

I have this same issue when running under OSX Mojave, the default terminal.

terrajobst · 2018-10-18T05:32:52Z

To be honest, I haven't tested Unix/macOS yet so I'd understand why that would fail. Not sure why the Windows ones fail though. I'll investigate.

terrajobst · 2018-10-18T05:35:26Z

worth to note that I am running Windows 7

Ah, just noticed you're on Win7. I'm on Win10. Maybe there is an accidental dependency somewhere that requires Win 10. I'll check.

shahabganji · 2018-10-18T06:11:42Z

Dear @terrajobst,

To be honest, I haven't tested Unix/macOS yet so I'd understand why that would fail. Not sure why the Windows ones fail though. I'll investigate.

I have also checked on Mac OSX ( macOS High Sierra Version 10.13.3 ), it does not even understand the istage command.

I did the following steps:

dotnet new install -g git-istage
In a git dircetory I ran : git istage .

and I failed with the an error message:

git: 'istage' is not a git command. See 'git --help'.

The most similar command is
	stage

here is the output for dotnet --info

.NET Core SDK (reflecting any global.json):
 Version:   2.2.100-preview2-009404
 Commit:    f4707d384d

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.13
 OS Platform: Darwin
 RID:         osx.10.13-x64
 Base Path:   /usr/local/share/dotnet/sdk/2.2.100-preview2-009404/

Host (useful for support):
  Version: 2.2.0-preview2-26905-02
  Commit:  ad4d306fe0

.NET Core SDKs installed:
  2.1.4 [/usr/local/share/dotnet/sdk]
  2.1.104 [/usr/local/share/dotnet/sdk]
  2.1.300-preview1-008174 [/usr/local/share/dotnet/sdk]
  2.1.300-rc1-008673 [/usr/local/share/dotnet/sdk]
  2.1.300 [/usr/local/share/dotnet/sdk]
  2.1.301 [/usr/local/share/dotnet/sdk]
  2.1.402 [/usr/local/share/dotnet/sdk]
  2.2.100-preview2-009404 [/usr/local/share/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.0-preview1-final [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.0-rc1-final [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.0 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.1 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.4 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.0-preview2-35157 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.0-preview1-final [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.0-rc1-final [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.0 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.1 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.4 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.0-preview2-35157 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.0.5 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.0.6 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.0-preview1-26216-03 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.0-rc1 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.0 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.1 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.4 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.0-preview2-26905-02 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

tiesmaster · 2018-10-18T17:59:27Z

@shahabganji Does the command $ git-istage even work (so without having git invoking istage)? Since that might be an issue with .NET Global tools. I have the same on ZSH. I have solved that by following @gabrielrb approach.

When I then run istage, from a git repository, I still get this (and mine issue #9).

shahabganji · 2018-10-18T18:53:49Z

I’ll take a look at the suggested approach and let you guys know about the result.

…

On Oct 18, 2018, at 21:30, Thijs Brobbel ***@***.***> wrote: @shahabganji Does the command $ git-istage even work (so without having git invoking istage)? Since that might be an issue with .NET Global tools. I have the same on ZSH. I have solved that by following @gabrielrb approach. When I then run istage, from a git repository, I still get this (and mine issue #9). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

shahabganji · 2018-10-22T03:50:55Z

@terrajobst , @tiesmaster

It still does not work on macOSX 10.13.3, I have added the dotnet tools folder to the PATH:

#Folders: 
export DOTNET_TOOLS_HOME=$HOME/.dotnet/tools

# Binaries:
export PATH=DOTNET_TOOLS_HOME:$PATH

however, when I run git-istage in the terminal it works, but when I run git istage it says no such a command found!

git: 'istage' is not a git command. See 'git --help'.

The most similar command is
	stage

My git versions is 2.16.2

Thanks anyway.

-------- EDIT ---------

To make it work env variables should be like the following, a $ is missed on the above snippet

#Folders: 
export DOTNET_TOOLS_HOME=$HOME/.dotnet/tools

# Binaries:
export PATH=$DOTNET_TOOLS_HOME:$PATH

shahabganji · 2018-10-22T05:41:08Z

@terrajobst , @tiesmaster

On my Windows 7 machine, the problem does exist too with the new version; and my git version on windows 7 is git version 2.9.0.windows.1.

PS 1: May find it fruitful to know that on my Mac machine I have dotnet 2.2.100-preview2-009404, and on my Windows 7 machine it is 2.1.403
PS 2: On Windows 7, Command Prompt has the same problem as I described for the Mac, In powershell it works just fine and seamlessly. In Git Bash Terminal( MINGW64 ) it is just as I described here

Thanks

tiesmaster · 2018-10-22T19:51:01Z

@shahabganji I'll check tomorrow on my Windows box.

terrajobst · 2018-10-22T22:51:16Z

owever, when I run git-istage in the terminal it works, but when I run git istage it says no such a command found!

That's bad. I believe that's tracked by #21 now.

@shahabganji

On my Windows 7 machine, the problem does exist too with the new version

What error do you get? I no longer call get_CursorVisible, so that must be something new then.

tiesmaster · 2018-10-23T08:29:33Z

I just upgraded from 0.2.2 to 0.2.29, and it's still failing under Git for Windows (using bash as shell), however, the stacktrace is now:

Unhandled Exception: System.IO.IOException: The handle is invalid
   at System.ConsolePal.set_CursorVisible(Boolean value)
   at GitIStage.Application.Run() in /home/vsts/work/1/s/src/git-istage/Application.cs:line 86
   at GitIStage.Program.Main() in /home/vsts/work/1/s/src/git-istage/Program.cs:line 32

Which makes sense, as usage of get_CursorVisible was removed in 9b9814e, however, set_CursorVisible is still there on L106.

shahabganji · 2018-10-23T11:21:58Z

@terrajobst

What error do you get? I no longer call get_CursorVisible, so that must be something new then.

Unhandled Exception: System.IO.IOException: The handle is invalid
   at System.ConsolePal.set_CursorVisible(Boolean value)
   at GitIStage.Application.Run() in /home/vsts/work/1/s/src/git-istage/Application.cs:line 86
   at GitIStage.Program.Main() in /home/vsts/work/1/s/src/git-istage/Program.cs:line 32

shahabganji · 2018-10-23T11:24:43Z

@tiesmaster

Can you also check on VS Code terminal, my VS Code terminal is set to Git Bash, and I don't get any error when running the command there.

CC: @terrajobst

tiesmaster · 2018-10-24T09:01:17Z

@shahabganji Ah, funny. Works in VS Code indeed. That's really odd...

tomaszprasolek · 2018-10-29T05:03:58Z

I also have that Exception, but when I launch git bash from path C:\Program Files\Git\bin\sh.exe it works normally. Default path for git bash for windows is: C:\Program Files\Git\git-bash.exe.

I work on Windows 8.1.

terrajobst mentioned this issue Oct 21, 2018

Fix Unix issues #20

Merged

terrajobst closed this as completed in #20 Oct 21, 2018

terrajobst mentioned this issue Oct 21, 2018

Running "git istage" doesn't work on Unix #21

Closed

terrajobst mentioned this issue Oct 22, 2018

git istage doesn't work after installation while git-istage does #22

Closed

terrajobst reopened this Oct 22, 2018

terrajobst changed the title ~~Unhandled Exception~~ Unhandled Exception on Windows 7 Dec 6, 2018

terrajobst added the bug label Nov 24, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Unhandled Exception on Windows 7 #12

Unhandled Exception on Windows 7 #12

shahabganji commented Oct 16, 2018 •

edited

Loading

drewnoakes commented Oct 16, 2018

shahabganji commented Oct 16, 2018 •

edited

Loading

drewnoakes commented Oct 16, 2018

shahabganji commented Oct 16, 2018

jvlppm commented Oct 17, 2018

terrajobst commented Oct 18, 2018 •

edited

Loading

terrajobst commented Oct 18, 2018 •

edited

Loading

shahabganji commented Oct 18, 2018 •

edited

Loading

tiesmaster commented Oct 18, 2018

shahabganji commented Oct 18, 2018 via email

shahabganji commented Oct 22, 2018 •

edited

Loading

shahabganji commented Oct 22, 2018 •

edited

Loading

tiesmaster commented Oct 22, 2018

terrajobst commented Oct 22, 2018 •

edited

Loading

tiesmaster commented Oct 23, 2018

shahabganji commented Oct 23, 2018

shahabganji commented Oct 23, 2018

tiesmaster commented Oct 24, 2018

tomaszprasolek commented Oct 29, 2018 •

edited

Loading

Unhandled Exception on Windows 7 #12

Unhandled Exception on Windows 7 #12

Comments

shahabganji commented Oct 16, 2018 • edited Loading

drewnoakes commented Oct 16, 2018

shahabganji commented Oct 16, 2018 • edited Loading

drewnoakes commented Oct 16, 2018

shahabganji commented Oct 16, 2018

jvlppm commented Oct 17, 2018

terrajobst commented Oct 18, 2018 • edited Loading

terrajobst commented Oct 18, 2018 • edited Loading

shahabganji commented Oct 18, 2018 • edited Loading

tiesmaster commented Oct 18, 2018

shahabganji commented Oct 18, 2018 via email

shahabganji commented Oct 22, 2018 • edited Loading

shahabganji commented Oct 22, 2018 • edited Loading

tiesmaster commented Oct 22, 2018

terrajobst commented Oct 22, 2018 • edited Loading

tiesmaster commented Oct 23, 2018

shahabganji commented Oct 23, 2018

shahabganji commented Oct 23, 2018

tiesmaster commented Oct 24, 2018

tomaszprasolek commented Oct 29, 2018 • edited Loading

shahabganji commented Oct 16, 2018 •

edited

Loading

shahabganji commented Oct 16, 2018 •

edited

Loading

terrajobst commented Oct 18, 2018 •

edited

Loading

terrajobst commented Oct 18, 2018 •

edited

Loading

shahabganji commented Oct 18, 2018 •

edited

Loading

shahabganji commented Oct 22, 2018 •

edited

Loading

shahabganji commented Oct 22, 2018 •

edited

Loading

terrajobst commented Oct 22, 2018 •

edited

Loading

tomaszprasolek commented Oct 29, 2018 •

edited

Loading