[NPE] on debug

[andxu]

| common.vscodeversion | 1.16.1
  | common.extversion | 0.1.0
  | common.osversion | 16.7.0
  | common.extname | vscode-java-debug
  | common.os | darwin
  | description | DebugSession dispatch exception: java.lang.NullPointerException
  | scope | exception
  | deubgSessionId | 7c0051c7-c171-4928-babb-461d27f88540

java.lang.NullPointerException at com.microsoft.java.debug.core.adapter.handler.SetBreakpointsRequestHandler.convertClientBreakpointsToDebugger(SetBreakpointsRequestHandler.java:119) at com.microsoft.java.debug.core.adapter.handler.SetBreakpointsRequestHandler.handle(SetBreakpointsRequestHandler.java:76) at com.microsoft.java.debug.core.adapter.DebugAdapter.dispatchRequest(DebugAdapter.java:73) at com.microsoft.java.debug.core.adapter.ProtocolServer.dispatchRequest(ProtocolServer.java:208) at com.microsoft.java.debug.core.adapter.ProtocolServer.processData(ProtocolServer.java:177) at com.microsoft.java.debug.core.adapter.ProtocolServer.start(ProtocolServer.java:99) at com.microsoft.java.debug.plugin.internal.JavaDebugServer$2.run(JavaDebugServer.java:139) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748)

[testforstephen]

The root cause is that VSCode still sends the setBreakpointRequest even if the debugger returns an error response for attach request. Will add null check at the debug session in the setBreakpointsRequestHandler.

[testforstephen]

fixed.