这是indexloc提供的服务,不要输入任何密码
Skip to content

dotnet try verify throws an exception when --destination-file is used #248

@jonsequitur

Description

@jonsequitur

Describe the bug

dotnet try verify throws an exception when --destination-file is used. Discovered while looking into #247.

Unhandled exception: System.ArgumentNullException: Value cannot be null.
Parameter name: path
   at WorkspaceServer.FileSystemDirectoryAccessor.GetFullyQualifiedPath(RelativePath path) in C:\dev\try\WorkspaceServer\FileSystemDirectoryAccessor.cs:line 61
   at MLS.Agent.Markdown.AnnotatedCodeBlockExtensions.GetBufferAsync(AnnotatedCodeBlock block, IDirectoryAccessor directoryAccessor, MarkdownFile markdownFile) in C:\dev\try\MLS.Agent\Markdown\AnnotatedCodeBlockExtensions.cs:line 19
   at MLS.Agent.CommandLine.VerifyCommand.<>c__DisplayClass0_1.<Do>b__12(AnnotatedCodeBlock block) in C:\dev\try\MLS.Agent\CommandLine\VerifyCommand.cs:line 141
   at System.Linq.Enumerable.SelectListIterator`2.ToList()
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at MLS.Agent.CommandLine.VerifyCommand.<>c__DisplayClass0_0.<<Do>g__ReportCompileResults|3>d.MoveNext() in C:\dev\try\MLS.Agent\CommandLine\VerifyCommand.cs:line 140
--- End of stack trace from previous location where exception was thrown ---
   at MLS.Agent.CommandLine.VerifyCommand.Do(VerifyOptions options, IConsole console, Func`1 getDirectoryAccessor, PackageRegistry packageRegistry, StartupOptions startupOptions) in C:\dev\try\MLS.Agent\CommandLine\VerifyCommand.cs:line 77
   at System.CommandLine.Invocation.CommandHandler.GetResultCodeAsync(Object value, InvocationContext context)
   at System.CommandLine.Invocation.ModelBindingCommandHandler.InvokeAsync(InvocationContext context)
   at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass2_0.<<InvokeAsync>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at MLS.Agent.CommandLine.CommandLineParser.<>c.<<Create>b__7_3>d.MoveNext() in C:\dev\try\MLS.Agent\CommandLine\CommandLineParser.cs:line 119
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Invocation.InvocationExtensions.<>c.<<UseParseErrorReporting>b__16_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Invocation.InvocationExtensions.<>c__DisplayClass8_0.<<UseTypoCorrections>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Invocation.InvocationExtensions.<>c.<<UseSuggestDirective>b__7_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Invocation.InvocationExtensions.<>c.<<UseParseDirective>b__6_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Invocation.InvocationExtensions.<>c.<<UseHelp>b__14_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass3_0.<<UseVersionOption>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Invocation.InvocationExtensions.<>c.<<RegisterWithDotnetSuggest>b__17_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Invocation.InvocationExtensions.<>c__DisplayClass5_0.<<UseExceptionHandler>b__0>d.MoveNext()

Did this error occur while using dotnet try or online?

  • dotnet-try
  • online

What kind of error was it?

  • User Interface (UI): For example the output never displayed
  • Service Error: For example "The service is temporarily unavailable. We are working on it"
  • Other: CLI

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions