CKAN Version: 1.22.3+64309722a446
Operating System: OS X
The issue you are experiencing:
When using the ckan binary on commandline, ckan available only lists mods until "KSPDev-LogConsole", and then bombs out with an error
How to recreate this issue:
on a fresh install of both KSP and CKAN on OSX:
mono ckan.exe update
mono ckan.exe available
CKAN error codes (if applicable):
Unhandled Exception:
System.FormatException: Input string was not in a correct format.
at System.Text.StringBuilder.AppendFormatHelper (IFormatProvider provider, System.String format, ParamsArray args) <0x1f53120 + 0x0020e> in <filename unknown>:0
at System.String.FormatHelper (IFormatProvider provider, System.String format, ParamsArray args) <0x1f3e280 + 0x00081> in <filename unknown>:0
at System.String.Format (IFormatProvider provider, System.String format, System.Object[] args) <0x1f3e1b0 + 0x000ba> in <filename unknown>:0
at System.IO.TextWriter.WriteLine (System.String format, System.Object[] arg) <0x1ea0b60 + 0x00037> in <filename unknown>:0
at System.IO.TextWriter+SyncTextWriter.WriteLine (System.String format, System.Object[] arg) <0x1ea24b0 + 0x0002e> in <filename unknown>:0
at (wrapper synchronized) System.IO.TextWriter+SyncTextWriter:WriteLine (string,object[])
at System.Console.WriteLine (System.String format, System.Object[] arg) <0x2171a60 + 0x00085> in <filename unknown>:0
at CKAN.CmdLine.ConsoleUser.DisplayMessage (System.String message, System.Object[] args) <0x826aac0 + 0x00017> in <filename unknown>:0
at CKAN.NullUser.RaiseMessage (System.String message, System.Object[] url) <0x826aa98 + 0x00022> in <filename unknown>:0
at CKAN.CmdLine.Available.RunCommand (CKAN.KSP ksp, System.Object raw_options) <0x825d308 + 0x00180> in <filename unknown>:0
at CKAN.CmdLine.MainClass.RunAction (CKAN.CmdLine.Options cmdline, CKAN.CmdLine.CommonOptions options, System.String[] args, IUser user, CKAN.KSPManager manager) <0x825c6f0 + 0x00523> in <filename unknown>:0
at CKAN.CmdLine.MainClass.Main (System.String[] args) <0x702150 + 0x009ab> in <filename unknown>:0
[ERROR] FATAL UNHANDLED EXCEPTION: System.FormatException: Input string was not in a correct format.
at System.Text.StringBuilder.AppendFormatHelper (IFormatProvider provider, System.String format, ParamsArray args) <0x1f53120 + 0x0020e> in <filename unknown>:0
at System.String.FormatHelper (IFormatProvider provider, System.String format, ParamsArray args) <0x1f3e280 + 0x00081> in <filename unknown>:0
at System.String.Format (IFormatProvider provider, System.String format, System.Object[] args) <0x1f3e1b0 + 0x000ba> in <filename unknown>:0
at System.IO.TextWriter.WriteLine (System.String format, System.Object[] arg) <0x1ea0b60 + 0x00037> in <filename unknown>:0
at System.IO.TextWriter+SyncTextWriter.WriteLine (System.String format, System.Object[] arg) <0x1ea24b0 + 0x0002e> in <filename unknown>:0
at (wrapper synchronized) System.IO.TextWriter+SyncTextWriter:WriteLine (string,object[])
at System.Console.WriteLine (System.String format, System.Object[] arg) <0x2171a60 + 0x00085> in <filename unknown>:0
at CKAN.CmdLine.ConsoleUser.DisplayMessage (System.String message, System.Object[] args) <0x826aac0 + 0x00017> in <filename unknown>:0
at CKAN.NullUser.RaiseMessage (System.String message, System.Object[] url) <0x826aa98 + 0x00022> in <filename unknown>:0
at CKAN.CmdLine.Available.RunCommand (CKAN.KSP ksp, System.Object raw_options) <0x825d308 + 0x00180> in <filename unknown>:0
at CKAN.CmdLine.MainClass.RunAction (CKAN.CmdLine.Options cmdline, CKAN.CmdLine.CommonOptions options, System.String[] args, IUser user, CKAN.KSPManager manager) <0x825c6f0 + 0x00523> in <filename unknown>:0
at CKAN.CmdLine.MainClass.Main (System.String[] args) <0x702150 + 0x009ab> in <filename unknown>:0
My hunch is that it has to do with the package KSPFrenchTranslation, as the errors allude to string encoding troubles, and the French language has a lot of non-standard characters.
Also, it follows right after KSPDev-LogConsole, which, as mentioned, is the last mod actually displayed.
This is fixed by #2111 .
oh excellent. Sorry for missing that one, didn't check the PRs.
Any prediction on the next release date?
Soon
The version with this fix is now released.