microsoft / microsoft/MIEngine

Silent Failure if putty does not accept host key

Open
#728 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
859
Forks
233
Avg merge
1d 6h
Merged PRs (30d)
3

Description

I am using MiEngine for remote debugging in VS2017. I am launching it using the following command:
DebugAdapterHost.Launch /LaunchJson:"C:\Dev\DockerDotnetDebug\DebugSample\MIEngineConfig\MIEngineAttach.json

Using the following Config file:

{
  "version": "0.2.0",
  "adapter": "plink.exe",
  "adapterArgs": "-l root -pw **** localhost -P 2222 -batch -T ~/vsdbg/vsdbg --interpreter=vscode",
  "languageMappings": {
    "C#": {
      "languageId": "3F5162F8-07C6-11D3-9053-00C04FA302A1",
      "extensions": [ "*" ]
    }
  },
  "exceptionCategoryMappings": {
    "CLR": "449EC4CC-30D2-4032-9256-EE18EB41B62B",
    "MDA": "6ECE07A9-0EDE-45C4-8296-818D8FC401D4"
  },
  "configurations": [
    {
      "name": ".NET Core Attach",
      "type": "coreclr",
      "request": "attach",
   "processName": "dotnet"
    }
  ]
}

I find that unless I have previously connected to this machine using putty and accepted the hostkey, the command will fail silently. It will give no error, and have no visible effect for the user. It was very difficult to try and identify what is actually wrong, if anything.
Is it possible to add at least some kind of output?

image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the DebugAdapterHost.Launch entry point and the plink.exe adapter invocation described in the issue. Reproduce the launch without an accepted host key, then trace how its failure is handled; done means the user receives visible error output instead of a silent failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.