search

badmotorfinger / z

Save time typing out directory paths in PowerShell by jumping around instead.
The Unlicense
426 stars 32 forks source link

Exception calling "Parse" with "1" argument(s): "Input string was not in a correct format." #5

Closed chaliy closed 9 years ago

chaliy commented 10 years ago

Not sure what is wrong. Ping me if you need more details.

C:\Users\Mike\Projects> $ cd .\studies-octo-adventure\ System.Management.Automation.MethodInvocationException: Exception calling "Parse" with "1" argument(s): "Input string was not in a correct format." ---> System.FormatException: Input string was not in a correct format. at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo numfmt) at CallSite.Target(Closure , CallSite , RuntimeType , Object ) --- End of inner exception stack trace --- at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception) at System.Management.Automation.Interpreter.ActionCallInstruction2.Run(InterpretedFrame frame) at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) at System.Management.Automation.Interpreter.Interpreter.Run(InterpretedFrame frame) at System.Management.Automation.Interpreter.LightLambda.RunVoid1[T0](T0 arg0) at System.Management.Automation.PSScriptCmdlet.RunClause(Action1 clause, Object dollarUnderbar, Object inputToProcess) at System.Management.Automation.PSScriptCmdlet.DoProcessRecord() at System.Management.Automation.CommandProcessor.ProcessRecord()

badmotorfinger commented 10 years ago

Hi Chaliy,

Can you explain how to reproduce this issue? I've tried installing it from scratch and CDing around and it "works for me" :)

Not a good start to adding my module to the PSGet directory. :(

chaliy commented 10 years ago

May be because I have custom prompt? I will try to take a look today.

/ Mike

From: Vince Panuccio Sent: ‎Thursday‎, ‎May‎ ‎29‎, ‎2014 ‎2‎:‎15‎ ‎AM To: vincpa/z Cc: Mike Chaliy

Hi Chaliy,

Can you explain how to reproduce this issue? I've tried installing it from scratch and CDing around and it "works for me" :)

Not a good start to adding my module to the PSGet directory. :(

— Reply to this email directly or view it on GitHub.

badmotorfinger commented 10 years ago

I tried a custom prompt also and no issues.

Which PowerShell version are you running? Also can you please try updating to the latest version?

kidchenko commented 9 years ago

+1

badmotorfinger commented 9 years ago

Do you also get this issue @kiide ?

kidchenko commented 9 years ago

@vincpa ops, sorry for delay, yes i get this issue to, same error :(

Konfekt commented 9 years ago

+1

Similar error:

Exception lors de l'appel de « Parse » avec « 1 » argument(s) : « Le format de la chaîne d'entrée est incorrect. »
Au caractère C:\Users\Enno\Documents\WindowsPowerShell\Modules\z\z.psm1:432 : 3
+         @{
+         ~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : FormatException

I am using PSReadline and Posh-Git.

kidchenko commented 9 years ago

I will fix it ahhaah

-----Original Message----- From: "Konfekt" notifications@github.com Sent: ‎12/‎19/‎2014 1:26 PM To: "vincpa/z" z@noreply.github.com Cc: "José Barbosa" kide.lemark@gmail.com Subject: Re: [z] Exception calling "Parse" with "1" argument(s): "Input stringwas not in a correct format." (#5)

+1 Same error. I am using PSReadline and Posh-Git. — Reply to this email directly or view it on GitHub.=

Konfekt commented 9 years ago

That would be nice. I am happy z exists for Powershell, thanks for porting it.

kidchenko commented 9 years ago

I am not a specialist in powershell, but i can try :)

-----Original Message----- From: "Konfekt" notifications@github.com Sent: ‎12/‎19/‎2014 2:51 PM To: "vincpa/z" z@noreply.github.com Cc: "José Barbosa" kide.lemark@gmail.com Subject: Re: [z] Exception calling "Parse" with "1" argument(s): "Input stringwas not in a correct format." (#5)

That would be nice. I am happy z exists for Powershell and thank you heartily for porting it. — Reply to this email directly or view it on GitHub.=

Konfekt commented 9 years ago

It must be messing with either Psreadline or poshgit if you use these. You should.

kidchenko commented 9 years ago

I use, i am try isolate the bug cause

-----Original Message----- From: "Konfekt" notifications@github.com Sent: ‎12/‎19/‎2014 3:24 PM To: "vincpa/z" z@noreply.github.com Cc: "José Barbosa" kide.lemark@gmail.com Subject: Re: [z] Exception calling "Parse" with "1" argument(s): "Input stringwas not in a correct format." (#5)

It must be messing with either Psreadline or poshgit if you use these. You should. — Reply to this email directly or view it on GitHub.=

badmotorfinger commented 9 years ago

Hi guys,

I will get this sorted tonight. I had no idea people were actually using this :)

@Konfekt - I have used z with and without RSReadLine without any issue. If someone could try running this without a profile loaded that would help me a lot in diagnosing this issue.

badmotorfinger commented 9 years ago

There is also a second commit which will read any existing broken cdhistory files. Simply reinstall via PSGet or copy the module manually.

Konfekt commented 9 years ago

Thank you. The problem was with the customized prompt by posh-git then?

badmotorfinger commented 9 years ago

The problem was that I was formatting a number without specifying an invariant culture. In Europe, numbers are formatted 0,000 and where I am from its 0.000 which caused an internal error during parsing the cdhistory data file.

-----Original Message----- From: "Konfekt" notifications@github.com Sent: ‎21/‎12/‎2014 23:20 To: "vincpa/z" z@noreply.github.com Cc: "Vince Panuccio" panuccio.vince@gmail.com Subject: Re: [z] Exception calling "Parse" with "1" argument(s): "Input stringwas not in a correct format." (#5)

Thank you. The problem was with the customized prompt by posh-git then? — Reply to this email directly or view it on GitHub.=

Konfekt commented 9 years ago

The problem disappears when using z for the first time right after updating but then returns. It is not fixed over here.

Note: The folder I tried to jump to by z dot contains a dot, it is .dotfiles, and it threw the same error message on second invocation of z dot.

kidchenko commented 9 years ago

Here too

-----Original Message----- From: "Konfekt" notifications@github.com Sent: ‎12/‎21/‎2014 10:51 AM To: "vincpa/z" z@noreply.github.com Cc: "José Barbosa" kide.lemark@gmail.com Subject: Re: [z] Exception calling "Parse" with "1" argument(s): "Input stringwas not in a correct format." (#5)

The problem disappears when using z for the first time right after updating but then returns. It is not fixed over here. — Reply to this email directly or view it on GitHub.=

badmotorfinger commented 9 years ago

OK I'll need to take another look.

badmotorfinger commented 9 years ago

OK so I tried this out with a directory which contains . and it works fine.

One thing that I should have mentioned is that after installing the updated module, you need to restart your Powershell session so it can load the module again otherwise the old one will reside in memory.

Can you please try this when you get a chance and please ensure you are using the latest version? I am eager to squash this bug.

Konfekt commented 9 years ago

Ok. I did as indicated. On typing cd .config there appeared

System.Management.Automation.MethodInvocationException: Exception lors de l'appel de « Parse » avec « 1 » argument(s) : « Le format de la chaîne d'entrée est incorrect. » ---> System.FormatException: Le format de la chaîne d'entrée est incorrect.
   à System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo numfmt)
   à CallSite.Target(Closure , CallSite , RuntimeType , Object )
   --- Fin de la trace de la pile d'exception interne ---
   à System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)
   à System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame)
   à System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
   à System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
   à System.Management.Automation.Interpreter.Interpreter.Run(InterpretedFrame frame)
   à System.Management.Automation.Interpreter.LightLambda.RunVoid1[T0](T0 arg0)
   à System.Management.Automation.PSScriptCmdlet.RunClause(Action`1 clause, Object dollarUnderbar, Object inputToProcess)
   à System.Management.Automation.PSScriptCmdlet.DoProcessRecord()
   à System.Management.Automation.CommandProcessor.ProcessRecord()
badmotorfinger commented 9 years ago

Running my PowerShell session in the fr-FR culture showed that an Invariant Culture parse was required. Please re-install the module and restart your session.

Konfekt commented 9 years ago

Ok, For me it's working now. Thanks!