text:
Docker-Typescript Debugger not working

I followed the recipe for setting up debugger for a Node-Typescript application inside Docker.
For some reason it is not working.
Below is my configuration as follows:
package.json (only scripts part):
{
  "scripts": {
      "tsc": "tsc -p ./tsconfig.json",
      "start": "node --no-lazy ./dist/server.js",
      "debug": "nodemon",
      "docker-compose-debug": "docker-compose up --force-recreate"
}

nodemon.json:
{
    "verbose": true,
    "ignore": ["*.spec.ts", "*.js"],
    "execMap": {
        "js": "node --no-lazy  --inspect-brk=9229"
    },
    "watch": "./dist",
    "ext": "js"
}

docker-compose:
version: '2.1'

services:
  cdt_box:
    container_name: cdt_box
    restart: always
    build: .
    image: app:dev
    entrypoint: ["npm", "run", "debug"]
    volumes:
      - ./dist:/server/dist
    ports:
      - 4000:4000
      - 9229:9229
    depends_on:
      - mongodb
    links: # soon deprecated
      - mongodb
  mongodb:
    image: mongo:3.6
    container_name: mongo
    volumes:
      - ./data/db:/data/db
    ports:
      - 27018:27017

tasks.json:
{
  "version": "2.0.0",
  "tasks": [
    {
      "label": "tsc-watch",
      "type": "typescript",
      "tsconfig": "tsconfig-dev.json",
      "problemMatcher": ["$tsc-watch"],
      "isBackground": true,
      "group": {
        "kind": "build",
        "isDefault": true
      },
      "presentation": {
        "reveal": "always",
        "panel": "new"
      }
    }
  ]
}

launch.json
Do I need to add  "address: localhost" in the 2nd configuration (attach)?
When I launch with "Launch Docker via npm" I can see that mongoose connects successfully and am able to hit the server with Postman. However the debugger times out.
{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "node",
      "request": "launch",
      "name": "Launch Docker via npm",
      "preLaunchTask": "tsc-watch",
      "runtimeExecutable": "npm",
      "runtimeArgs": ["run", "docker-compose-debug"],
      "localRoot": "${workspaceFolder}",
      "remoteRoot": "/server",
      "outFiles": ["${workspaceFolder}/dist/**/*.js"],
      "console": "integratedTerminal",
      "internalConsoleOptions": "neverOpen",
      "protocol": "inspector",
      "port": 9229,
      "timeout": 60000,
      "sourceMaps": true,
      "restart": true
    },
    {
      "type": "node",
      "request": "attach",
      "name": "Docker: Attach to Node",
      "preLaunchTask": "tsc-watch",
      "localRoot": "${workspaceFolder}",
      "remoteRoot": "/server",
      "outFiles": ["${workspaceFolder}/dist/**/*.js"],
      "internalConsoleOptions": "openOnFirstSessionStart",
      "restart": true,
      "sourceMaps": true,
      "port": 9229,
      "protocol": "inspector"
    },
    {
      "type": "node",
      "request": "launch",
      "name": "nodemon-npm",
      "preLaunchTask": "tsc-watch",
      "cwd": "${workspaceFolder}",
      "runtimeExecutable": "npm",
      "program": "${workspaceFolder}/dist/server.js",
      "runtimeArgs": ["run-script", "debug"],
      "restart": true,
      "sourceMaps": true,
      "outFiles": ["${workspaceFolder}/dist/**/*.js"],
      "console": "integratedTerminal",
      "internalConsoleOptions": "neverOpen",
      "protocol": "inspector",
      "port": 9229
    }
  ]
}

@barakbd Can you try to add trace: true to your debug configuration and attach the log from your debug console here?

I created a demo project you can just clone and run.

OS: darwin x64
Adapter node: v7.9.0 x64
vscode-chrome-debug-core: 4.2.2
13:58:10, 2018-5-2
node-debug2: 1.23.5
From client: initialize({"clientID":"vscode","clientName":"Visual Studio Code - Insiders","adapterID":"node2","pathFormat":"path","linesStartAt1":true,"columnsStartAt1":true,"supportsVariableType":true,"supportsVariablePaging":true,"supportsRunInTerminalRequest":true,"locale":"en-us"})
To client: {"seq":0,"type":"response","request_seq":1,"command":"initialize","success":true,"body":{"exceptionBreakpointFilters":[{"label":"All Exceptions","filter":"all","default":false},{"label":"Uncaught Exceptions","filter":"uncaught","default":false}],"supportsConfigurationDoneRequest":true,"supportsSetVariable":true,"supportsConditionalBreakpoints":true,"supportsCompletionsRequest":true,"supportsHitConditionalBreakpoints":true,"supportsRestartFrame":true,"supportsExceptionInfoRequest":true,"supportsDelayedStackTraceLoading":true,"supportsValueFormattingOptions":true,"supportsEvaluateForHovers":true,"supportsLogPoints":true}}
To client: {"seq":0,"type":"event","event":"output","body":{"category":"telemetry","output":"ClientRequest/initialize","data":{"Versions.DebugAdapterCore":"4.2.2","Versions.DebugAdapter":"1.23.5","successful":"true","timeTakenInMilliseconds":"3.142347","requestType":"request"}}}
From client: attach({"type":"node2","request":"attach","name":"Docker: Attach to Node","preLaunchTask":"tsc-watch","localRoot":"/Users/bbendavi/Documents/docker_typescript_debug_vscode","remoteRoot":"/server","outFiles":["/Users/bbendavi/Documents/docker_typescript_debug_vscode/dist//*.js"],"sourceMaps":true,"address":"localhost","port":9225,"protocol":"inspector","trace":true,"cwd":"/Users/bbendavi/Documents/docker_typescript_debug_vscode","logFilePath":"/Users/bbendavi/Library/Application Support/Code - Insiders/logs/20180501T134606/ms-vscode.node-debug_4/debugadapter.txt","__sessionId":"a8e78e04-1721-4e50-9313-ba7678308ec0"})
SourceMaps: preloading sourcemaps for scripts in globs: ["/Users/bbendavi/Documents/docker_typescript_debug_vscode/dist//*.js"]
To client: {"seq":0,"type":"event","event":"output","body":{"category":"telemetry","output":"debugStarted","data":{"Versions.DebugAdapterCore":"4.2.2","Versions.DebugAdapter":"1.23.5","request":"attach","args":["type","request","name","preLaunchTask","localRoot","remoteRoot","outFiles","sourceMaps","address","port","protocol","trace","cwd","logFilePath","__sessionId","sourceMapPathOverrides","showAsyncStacks"]}}}
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
SourceMaps: expanded globs and found 10 scripts
SourceMaps: sourcemap url parsed from end of generated content: data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiYXBwLmpzIiwic291cmNlUm9vdCI6IiIsInNvdXJjZXMiOlsiLi4vc3JjL2FwcC50cyJdLCJuYW1lcyI6W10sIm1hcHBpbmdzIjoiOztBQUFBLG1DQUFtQztBQUNuQywwQ0FBMEM7QUFDMUMsNENBQTRDO0FBQzVDLDRFQUFzRTtBQUV0RSxNQUFNLEdBQUcsR0FBd0IsT0FBTyxFQUFFLENBQUM7QUFlbEMsa0JBQUc7QUFkWixHQUFHLENBQUMsR0FBRyxDQUFDLFVBQVUsQ0FBQyxJQUFJLEVBQUUsQ0FBQyxDQUFDO0FBQzNCLEdBQUcsQ0FBQyxHQUFHLENBQ0wsVUFBVSxDQUFDLFVBQVUsQ0FBQztJQUNwQixRQUFRLEVBQUUsS0FBSztDQUNoQixDQUFDLENBQ0gsQ0FBQztBQUNGLEdBQUcsQ0FBQyxHQUFHLENBQUMsZUFBZSxFQUFFLENBQUMsR0FBRyxFQUFFLEdBQUcsRUFBRSxFQUFFO0lBQ3BDLE9BQU8sQ0FBQyxHQUFHLENBQUMsdUJBQXVCLENBQUMsQ0FBQztJQUNyQyxHQUFHLENBQUMsSUFBSSxDQUFDO1FBQ1AsT0FBTyxFQUFFLGNBQWMsR0FBRyxDQUFDLE1BQU0sQ0FBQyxNQUFNLEdBQUc7S0FDNUMsQ0FBQyxDQUFDO0FBQ0wsQ0FBQyxDQUFDLENBQUM7QUFDSCxHQUFHLENBQUMsR0FBRyxDQUFDLGtCQUFTLENBQUMsQ0FBQztBQUNuQixHQUFHLENBQUMsR0FBRyxDQUFDLDRDQUFtQixDQUFDLENBQUMifQ==
SourceMaps.getMapForGeneratedPath: Finding SourceMap for /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/app.js by URI: data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiYXBwLmpzIiwic291cmNlUm9vdCI6IiIsInNvdXJjZXMiOlsiLi4vc3JjL2FwcC50cyJdLCJuYW1lcyI6W10sIm1hcHBpbmdzIjoiOztBQUFBLG1DQUFtQztBQUNuQywwQ0FBMEM7QUFDMUMsNENBQTRDO0FBQzVDLDRFQUFzRTtBQUV0RSxNQUFNLEdBQUcsR0FBd0IsT0FBTyxFQUFFLENBQUM7QUFlbEMsa0JBQUc7QUFkWixHQUFHLENBQUMsR0FBRyxDQUFDLFVBQVUsQ0FBQyxJQUFJLEVBQUUsQ0FBQyxDQUFDO0FBQzNCLEdBQUcsQ0FBQyxHQUFHLENBQ0wsVUFBVSxDQUFDLFVBQVUsQ0FBQztJQUNwQixRQUFRLEVBQUUsS0FBSztDQUNoQixDQUFDLENBQ0gsQ0FBQztBQUNGLEdBQUcsQ0FBQyxHQUFHLENBQUMsZUFBZSxFQUFFLENBQUMsR0FBRyxFQUFFLEdBQUcsRUFBRSxFQUFFO0lBQ3BDLE9BQU8sQ0FBQyxHQUFHLENBQUMsdUJBQXVCLENBQUMsQ0FBQztJQUNyQyxHQUFHLENBQUMsSUFBSSxDQUFDO1FBQ1AsT0FBTyxFQUFFLGNBQWMsR0FBRyxDQUFDLE1BQU0sQ0FBQyxNQUFNLEdBQUc7S0FDNUMsQ0FBQyxDQUFDO0FBQ0wsQ0FBQyxDQUFDLENBQUM7QUFDSCxHQUFHLENBQUMsR0FBRyxDQUFDLGtCQUFTLENBQUMsQ0FBQztBQUNuQixHQUFHLENBQUMsR0FBRyxDQUFDLDRDQUFtQixDQUFDLENBQUMifQ==
SourceMaps.getMapForGeneratedPath: Using inlined sourcemap in /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/app.js
SourceMap: creating for /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/app.js
SourceMap: sourceRoot:
SourceMap: sources: ["../src/app.ts"]
SourceMap: no sourceRoot specified, using script dirname: /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist
SourceMaps: sourcemap url parsed from end of generated content: data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiYXBwLnNwZWMuanMiLCJzb3VyY2VSb290IjoiIiwic291cmNlcyI6WyIuLi9zcmMvYXBwLnNwZWMudHMiXSwibmFtZXMiOltdLCJtYXBwaW5ncyI6Ijs7QUFDQSxPQUFPLENBQUMsR0FBRyxDQUFDLDRCQUE0QixDQUFDLENBQUM7QUFJMUMsK0JBQTREO0FBQzVELHNDQUF1QztBQUd2QywrQkFBNEI7QUFDNUIsVUFBRyxDQUFDLFFBQVEsQ0FBQyxDQUFDO0FBQ2QsUUFBUSxDQUFDLFdBQVcsRUFBRSxHQUFHLEVBQUU7SUFDekIsRUFBRSxDQUFDLDJDQUEyQyxFQUFFLEdBQUcsRUFBRTtRQUNuRCxNQUFNLE1BQU0sR0FBVyxTQUFTLENBQUM7UUFDakMsY0FBTyxDQUFDLFNBQUcsQ0FBQzthQUNULEdBQUcsQ0FBQyxTQUFTLE1BQU0sRUFBRSxDQUFDO2FBRXRCLEdBQUcsQ0FBQyxDQUFDLEdBQUcsRUFBRSxHQUFHLEVBQUUsRUFBRTtZQUNoQixPQUFPLENBQUMsR0FBRyxDQUFDLFFBQVEsRUFBRSxTQUFHLENBQUMsQ0FBQztZQUMzQixJQUFJO2dCQUNGLGFBQU0sQ0FBQyxHQUFHLENBQUMsQ0FBQztnQkFDWixhQUFNLENBQUMsR0FBRyxDQUFDLElBQUksQ0FBQyxDQUFDLEVBQUUsQ0FBQyxHQUFHLENBQUMsS0FBSyxDQUFDLElBQUksQ0FBQyxDQUFDO2dCQUNwQyxhQUFNLENBQUMsR0FBRyxDQUFDLElBQUksQ0FBQyxDQUFDLEVBQUUsQ0FBQyxFQUFFLENBQUMsd0JBQXdCLE1BQU0sSUFBSSxDQUFDLENBQUM7YUFHNUQ7WUFBQyxPQUFPLEdBQUcsRUFBRTthQUViO1FBQ0gsQ0FBQyxDQUFDLENBQUM7SUFDUCxDQUFDLENBQUMsQ0FBQztBQUNMLENBQUMsQ0FBQyxDQUFDIn0=
SourceMaps.getMapForGeneratedPath: Finding SourceMap for /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/app.spec.js by URI: data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiYXBwLnNwZWMuanMiLCJzb3VyY2VSb290IjoiIiwic291cmNlcyI6WyIuLi9zcmMvYXBwLnNwZWMudHMiXSwibmFtZXMiOltdLCJtYXBwaW5ncyI6Ijs7QUFDQSxPQUFPLENBQUMsR0FBRyxDQUFDLDRCQUE0QixDQUFDLENBQUM7QUFJMUMsK0JBQTREO0FBQzVELHNDQUF1QztBQUd2QywrQkFBNEI7QUFDNUIsVUFBRyxDQUFDLFFBQVEsQ0FBQyxDQUFDO0FBQ2QsUUFBUSxDQUFDLFdBQVcsRUFBRSxHQUFHLEVBQUU7SUFDekIsRUFBRSxDQUFDLDJDQUEyQyxFQUFFLEdBQUcsRUFBRTtRQUNuRCxNQUFNLE1BQU0sR0FBVyxTQUFTLENBQUM7UUFDakMsY0FBTyxDQUFDLFNBQUcsQ0FBQzthQUNULEdBQUcsQ0FBQyxTQUFTLE1BQU0sRUFBRSxDQUFDO2FBRXRCLEdBQUcsQ0FBQyxDQUFDLEdBQUcsRUFBRSxHQUFHLEVBQUUsRUFBRTtZQUNoQixPQUFPLENBQUMsR0FBRyxDQUFDLFFBQVEsRUFBRSxTQUFHLENBQUMsQ0FBQztZQUMzQixJQUFJO2dCQUNGLGFBQU0sQ0FBQyxHQUFHLENBQUMsQ0FBQztnQkFDWixhQUFNLENBQUMsR0FBRyxDQUFDLElBQUksQ0FBQyxDQUFDLEVBQUUsQ0FBQyxHQUFHLENBQUMsS0FBSyxDQUFDLElBQUksQ0FBQyxDQUFDO2dCQUNwQyxhQUFNLENBQUMsR0FBRyxDQUFDLElBQUksQ0FBQyxDQUFDLEVBQUUsQ0FBQyxFQUFFLENBQUMsd0JBQXdCLE1BQU0sSUFBSSxDQUFDLENBQUM7YUFHNUQ7WUFBQyxPQUFPLEdBQUcsRUFBRTthQUViO1FBQ0gsQ0FBQyxDQUFDLENBQUM7SUFDUCxDQUFDLENBQUMsQ0FBQztBQUNMLENBQUMsQ0FBQyxDQUFDIn0=
SourceMaps.getMapForGeneratedPath: Using inlined sourcemap in /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/app.spec.js
SourceMap: creating for /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/app.spec.js
SourceMap: sourceRoot:
SourceMap: sources: ["../src/app.spec.ts"]
SourceMap: no sourceRoot specified, using script dirname: /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist
SourceMaps: sourcemap url parsed from end of generated content: data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiZXJyb3JfcmVxdWVzdF9oYW5kbGVycy5qcyIsInNvdXJjZVJvb3QiOiIiLCJzb3VyY2VzIjpbIi4uLy4uL3NyYy9jb25maWcvZXJyb3JfcmVxdWVzdF9oYW5kbGVycy50cyJdLCJuYW1lcyI6W10sIm1hcHBpbmdzIjoiOztBQUdhLFFBQUEsbUJBQW1CLEdBQXdCLENBQ3RELEdBQUcsRUFDSCxHQUFHLEVBQ0gsR0FBRyxFQUNILElBQUksRUFDSixFQUFFO0lBQ0YsSUFBSSxHQUFHLENBQUMsV0FBVyxFQUFFO1FBQ25CLE9BQU8sSUFBSSxDQUFDLEdBQUcsQ0FBQyxDQUFDO0tBQ2xCO0lBQ0QsT0FBTyxDQUFDLEdBQUcsQ0FBQywwQ0FBMEMsQ0FBQyxDQUFDO0lBQ3hELEdBQUcsQ0FBQyxNQUFNLENBQUMsR0FBRyxDQUFDLENBQUM7SUFDaEIsR0FBRyxDQUFDLElBQUksQ0FBQyxHQUFHLENBQUMsQ0FBQztBQUNoQixDQUFDLENBQUMifQ==
SourceMaps.getMapForGeneratedPath: Finding SourceMap for /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/config/error_request_handlers.js by URI: data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiZXJyb3JfcmVxdWVzdF9oYW5kbGVycy5qcyIsInNvdXJjZVJvb3QiOiIiLCJzb3VyY2VzIjpbIi4uLy4uL3NyYy9jb25maWcvZXJyb3JfcmVxdWVzdF9oYW5kbGVycy50cyJdLCJuYW1lcyI6W10sIm1hcHBpbmdzIjoiOztBQUdhLFFBQUEsbUJBQW1CLEdBQXdCLENBQ3RELEdBQUcsRUFDSCxHQUFHLEVBQ0gsR0FBRyxFQUNILElBQUksRUFDSixFQUFFO0lBQ0YsSUFBSSxHQUFHLENBQUMsV0FBVyxFQUFFO1FBQ25CLE9BQU8sSUFBSSxDQUFDLEdBQUcsQ0FBQyxDQUFDO0tBQ2xCO0lBQ0QsT0FBTyxDQUFDLEdBQUcsQ0FBQywwQ0FBMEMsQ0FBQyxDQUFDO0lBQ3hELEdBQUcsQ0FBQyxNQUFNLENBQUMsR0FBRyxDQUFDLENBQUM7SUFDaEIsR0FBRyxDQUFDLElBQUksQ0FBQyxHQUFHLENBQUMsQ0FBQztBQUNoQixDQUFDLENBQUMifQ==
SourceMaps.getMapForGeneratedPath: Using inlined sourcemap in /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/config/error_request_handlers.js
SourceMap: creating for /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/config/error_request_handlers.js
SourceMap: sourceRoot:
SourceMap: sources: ["../../src/config/error_request_handlers.ts"]
SourceMap: no sourceRoot specified, using script dirname: /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/config
SourceMaps: sourcemap url parsed from end of generated content: data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoibW9uZ29vc2VfY29ubmVjdGlvbi5qcyIsInNvdXJjZVJvb3QiOiIiLCJzb3VyY2VzIjpbIi4uLy4uL3NyYy9jb25maWcvbW9uZ29vc2VfY29ubmVjdGlvbi50cyJdLCJuYW1lcyI6W10sIm1hcHBpbmdzIjoiOztBQUNBLHFDQUFxQztBQUNyQyxJQUFJLGlCQUF5RCxDQUFDO0FBRTlELE1BQU0sR0FBRyxHQUFXLGFBQWEsT0FBTyxDQUFDLEdBQUcsQ0FBQywwQkFBMEIsSUFDckUsT0FBTyxDQUFDLEdBQUcsQ0FBQyxxQkFDZCxFQUFFLENBQUM7QUFFSCxPQUFPLENBQUMsR0FBRyxDQUFDLEtBQUssRUFBRSxHQUFHLENBQUMsQ0FBQztBQUN4QixNQUFNLHlCQUF5QixHQUErQjtJQUM1RCxhQUFhLEVBQUUsSUFBSTtJQUNuQixjQUFjLEVBQUUsQ0FBQztJQUNqQixTQUFTLEVBQUUsR0FBRztJQUNkLElBQUksRUFBRSxPQUFPLENBQUMsR0FBRyxDQUFDLG1CQUFtQjtJQUNyQyxJQUFJLEVBQUUsT0FBTyxDQUFDLEdBQUcsQ0FBQyxtQkFBbUI7SUFDckMsVUFBVSxFQUFFLE9BQU8sQ0FBQyxHQUFHLENBQUMsbUJBQW1CO0lBQzNDLFVBQVUsRUFBRSxPQUFPLENBQUMsR0FBRyxDQUFDLGtCQUFrQjtDQUMzQyxDQUFDO0FBRUYsT0FBTyxDQUFDLEdBQUcsQ0FBQyxRQUFRLEtBQUssT0FBTztJQUM5QixDQUFDLENBQUMsQ0FBQyxpQkFBaUIsR0FBRyxTQUFTLENBQUM7SUFDakMsQ0FBQyxDQUFDLENBQUMsaUJBQWlCLEdBQUcseUJBQXlCLENBQUMsQ0FBQztBQUVwRCxPQUFPLENBQUMsR0FBRyxDQUFDLCtCQUErQixFQUFFLGlCQUFpQixDQUFDLENBQUM7QUFFaEUsUUFBUTtLQUNMLE9BQU8sQ0FBQyxHQUFHLEVBQUUsaUJBQWlCLENBQUM7S0FDL0IsSUFBSSxDQUFDLEdBQUcsRUFBRTtJQUNULE9BQU8sQ0FBQyxJQUFJLENBQUMsMkJBQTJCLENBQUMsQ0FBQztBQUc1QyxDQUFDLENBQUM7S0FDRCxLQUFLLENBQUMsQ0FBQyxHQUFtQixFQUFFLEVBQUU7SUFDN0IsT0FBTyxDQUFDLEtBQUssQ0FBQyw0QkFBNEIsRUFBRSxHQUFHLENBQUMsQ0FBQztJQUVqRCxPQUFPLENBQUMsSUFBSSxDQUFDLE9BQU8sQ0FBQyxHQUFHLENBQUMsQ0FBQztBQUM1QixDQUFDLENBQUMsQ0FBQztBQUNMLE1BQU0sa0JBQWtCLEdBQXdCLFFBQVEsQ0FBQyxVQUFVLENBQUM7QUFDM0QsZ0RBQWtCIn0=
SourceMaps.getMapForGeneratedPath: Finding SourceMap for /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/config/mongoose_connection.js by URI: data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoibW9uZ29vc2VfY29ubmVjdGlvbi5qcyIsInNvdXJjZVJvb3QiOiIiLCJzb3VyY2VzIjpbIi4uLy4uL3NyYy9jb25maWcvbW9uZ29vc2VfY29ubmVjdGlvbi50cyJdLCJuYW1lcyI6W10sIm1hcHBpbmdzIjoiOztBQUNBLHFDQUFxQztBQUNyQyxJQUFJLGlCQUF5RCxDQUFDO0FBRTlELE1BQU0sR0FBRyxHQUFXLGFBQWEsT0FBTyxDQUFDLEdBQUcsQ0FBQywwQkFBMEIsSUFDckUsT0FBTyxDQUFDLEdBQUcsQ0FBQyxxQkFDZCxFQUFFLENBQUM7QUFFSCxPQUFPLENBQUMsR0FBRyxDQUFDLEtBQUssRUFBRSxHQUFHLENBQUMsQ0FBQztBQUN4QixNQUFNLHlCQUF5QixHQUErQjtJQUM1RCxhQUFhLEVBQUUsSUFBSTtJQUNuQixjQUFjLEVBQUUsQ0FBQztJQUNqQixTQUFTLEVBQUUsR0FBRztJQUNkLElBQUksRUFBRSxPQUFPLENBQUMsR0FBRyxDQUFDLG1CQUFtQjtJQUNyQyxJQUFJLEVBQUUsT0FBTyxDQUFDLEdBQUcsQ0FBQyxtQkFBbUI7SUFDckMsVUFBVSxFQUFFLE9BQU8sQ0FBQyxHQUFHLENBQUMsbUJBQW1CO0lBQzNDLFVBQVUsRUFBRSxPQUFPLENBQUMsR0FBRyxDQUFDLGtCQUFrQjtDQUMzQyxDQUFDO0FBRUYsT0FBTyxDQUFDLEdBQUcsQ0FBQyxRQUFRLEtBQUssT0FBTztJQUM5QixDQUFDLENBQUMsQ0FBQyxpQkFBaUIsR0FBRyxTQUFTLENBQUM7SUFDakMsQ0FBQyxDQUFDLENBQUMsaUJBQWlCLEdBQUcseUJBQXlCLENBQUMsQ0FBQztBQUVwRCxPQUFPLENBQUMsR0FBRyxDQUFDLCtCQUErQixFQUFFLGlCQUFpQixDQUFDLENBQUM7QUFFaEUsUUFBUTtLQUNMLE9BQU8sQ0FBQyxHQUFHLEVBQUUsaUJBQWlCLENBQUM7S0FDL0IsSUFBSSxDQUFDLEdBQUcsRUFBRTtJQUNULE9BQU8sQ0FBQyxJQUFJLENBQUMsMkJBQTJCLENBQUMsQ0FBQztBQUc1QyxDQUFDLENBQUM7S0FDRCxLQUFLLENBQUMsQ0FBQyxHQUFtQixFQUFFLEVBQUU7SUFDN0IsT0FBTyxDQUFDLEtBQUssQ0FBQyw0QkFBNEIsRUFBRSxHQUFHLENBQUMsQ0FBQztJQUVqRCxPQUFPLENBQUMsSUFBSSxDQUFDLE9BQU8sQ0FBQyxHQUFHLENBQUMsQ0FBQztBQUM1QixDQUFDLENBQUMsQ0FBQztBQUNMLE1BQU0sa0JBQWtCLEdBQXdCLFFBQVEsQ0FBQyxVQUFVLENBQUM7QUFDM0QsZ0RBQWtCIn0=
SourceMaps.getMapForGeneratedPath: Using inlined sourcemap in /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/config/mongoose_connection.js
SourceMap: creating for /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/config/mongoose_connection.js
SourceMap: sourceRoot:
SourceMap: sources: ["../../src/config/mongoose_connection.ts"]
SourceMap: no sourceRoot specified, using script dirname: /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/config
SourceMaps: sourcemap url parsed from end of generated content: data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoicm91dGVzLmpzIiwic291cmNlUm9vdCI6IiIsInNvdXJjZXMiOlsiLi4vLi4vc3JjL2NvbmZpZy9yb3V0ZXMudHMiXSwibmFtZXMiOltdLCJtYXBwaW5ncyI6Ijs7QUFJQSxxQ0FBMEM7QUFDMUMsMkJBQWlDO0FBQ2pDLCtCQUFzQztBQUV0QyxNQUFNLE1BQU0sR0FBRyxlQUFlLENBQUM7QUFDL0IsTUFBTSxTQUFTLEdBQVcsZ0JBQU0sRUFBRSxDQUFDO0FBa0IxQiw4QkFBUztBQWhCbEIsZ0JBQVcsQ0FBQyxXQUFJLENBQUMsU0FBUyxFQUFFLGdCQUFnQixDQUFDLENBQUM7S0FDM0MsTUFBTSxDQUFDLENBQUMsUUFBZ0IsRUFBRSxFQUFFO0lBQzNCLE9BQU8sUUFBUSxJQUFJLFlBQVksSUFBSSxRQUFRLEtBQUssc0JBQXNCLENBQUM7QUFDekUsQ0FBQyxDQUFDO0tBQ0QsT0FBTyxDQUFDLGNBQWMsQ0FBQyxFQUFFO0lBQ3hCLE1BQU0sa0JBQWtCLEdBQUcsZUFBUSxDQUFDLGNBQWMsRUFBRSxLQUFLLENBQUMsQ0FBQztJQUUzRCxxQ0FBTyxrQkFBa0Isa0JBQWtCLEVBQUUsR0FDMUMsSUFBSSxDQUFDLFVBQVUsQ0FBQyxFQUFFO1FBQ2pCLFNBQVMsQ0FBQyxHQUFHLENBQUMsSUFBSSxrQkFBa0IsRUFBRSxFQUFFLFVBQVUsQ0FBQyxPQUFPLENBQUMsTUFBTSxDQUFDLENBQUMsQ0FBQztJQUN0RSxDQUFDLENBQUM7U0FDRCxLQUFLLENBQUMsS0FBSyxDQUFDLEVBQUU7UUFDYixPQUFPLENBQUMsR0FBRyxDQUFDLEtBQUssQ0FBQyxDQUFDO0lBQ3JCLENBQUMsQ0FBQyxDQUFDO0FBQ1AsQ0FBQyxDQUFDLENBQUMifQ==
SourceMaps.getMapForGeneratedPath: Finding SourceMap for /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/config/routes.js by URI: data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoicm91dGVzLmpzIiwic291cmNlUm9vdCI6IiIsInNvdXJjZXMiOlsiLi4vLi4vc3JjL2NvbmZpZy9yb3V0ZXMudHMiXSwibmFtZXMiOltdLCJtYXBwaW5ncyI6Ijs7QUFJQSxxQ0FBMEM7QUFDMUMsMkJBQWlDO0FBQ2pDLCtCQUFzQztBQUV0QyxNQUFNLE1BQU0sR0FBRyxlQUFlLENBQUM7QUFDL0IsTUFBTSxTQUFTLEdBQVcsZ0JBQU0sRUFBRSxDQUFDO0FBa0IxQiw4QkFBUztBQWhCbEIsZ0JBQVcsQ0FBQyxXQUFJLENBQUMsU0FBUyxFQUFFLGdCQUFnQixDQUFDLENBQUM7S0FDM0MsTUFBTSxDQUFDLENBQUMsUUFBZ0IsRUFBRSxFQUFFO0lBQzNCLE9BQU8sUUFBUSxJQUFJLFlBQVksSUFBSSxRQUFRLEtBQUssc0JBQXNCLENBQUM7QUFDekUsQ0FBQyxDQUFDO0tBQ0QsT0FBTyxDQUFDLGNBQWMsQ0FBQyxFQUFFO0lBQ3hCLE1BQU0sa0JBQWtCLEdBQUcsZUFBUSxDQUFDLGNBQWMsRUFBRSxLQUFLLENBQUMsQ0FBQztJQUUzRCxxQ0FBTyxrQkFBa0Isa0JBQWtCLEVBQUUsR0FDMUMsSUFBSSxDQUFDLFVBQVUsQ0FBQyxFQUFFO1FBQ2pCLFNBQVMsQ0FBQyxHQUFHLENBQUMsSUFBSSxrQkFBa0IsRUFBRSxFQUFFLFVBQVUsQ0FBQyxPQUFPLENBQUMsTUFBTSxDQUFDLENBQUMsQ0FBQztJQUN0RSxDQUFDLENBQUM7U0FDRCxLQUFLLENBQUMsS0FBSyxDQUFDLEVBQUU7UUFDYixPQUFPLENBQUMsR0FBRyxDQUFDLEtBQUssQ0FBQyxDQUFDO0lBQ3JCLENBQUMsQ0FBQyxDQUFDO0FBQ1AsQ0FBQyxDQUFDLENBQUMifQ==
SourceMaps.getMapForGeneratedPath: Using inlined sourcemap in /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/config/routes.js
SourceMap: creating for /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/config/routes.js
SourceMap: sourceRoot:
SourceMap: sources: ["../../src/config/routes.ts"]
SourceMap: no sourceRoot specified, using script dirname: /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/config
SourceMaps: sourcemap url parsed from end of generated content: data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiZmlsZXMuanMiLCJzb3VyY2VSb290IjoiIiwic291cmNlcyI6WyIuLi8uLi9zcmMvY29udHJvbGxlcnMvZmlsZXMudHMiXSwibmFtZXMiOltdLCJtYXBwaW5ncyI6Ijs7QUFBQSxxQ0FNaUI7QUFFakIseUNBQWlEO0FBR2pEO0lBS0UsWUFBWSxNQUFjO1FBa0JsQixZQUFPLEdBQW1CLENBQ2hDLEdBQVksRUFDWixHQUFhLEVBQ2IsSUFBa0IsRUFDQyxFQUFFO1lBQ3JCLElBQUksT0FBTyxHQUF1QixJQUFJLGdCQUFTLEVBQUUsQ0FBQztZQUNsRCxPQUFPLENBQUMsU0FBUyxHQUFHLElBQUksQ0FBQyxPQUFPLEdBQUcsR0FBRyxDQUFDLElBQUksQ0FBQyxTQUFTLENBQUM7WUFFdEQsT0FBTyxPQUFPO2lCQUNYLElBQUksRUFBRTtpQkFDTixJQUFJLENBQUMsQ0FBQyxrQkFBaUQsRUFBRSxFQUFFO2dCQUMxRCxPQUFPLEdBQUcsQ0FBQyxNQUFNLENBQUMsR0FBRyxDQUFDLENBQUMsSUFBSSxDQUFDLGtCQUFrQixDQUFDLENBQUM7WUFDbEQsQ0FBQyxDQUFDO2lCQUNELEtBQUssQ0FBQyxDQUFDLGdCQUFnQyxFQUFFLEVBQUU7Z0JBRTFDLE9BQU8sR0FBRyxDQUFDLE1BQU0sQ0FBQyxHQUFHLENBQUMsQ0FBQyxJQUFJLENBQUMsZ0JBQWdCLENBQUMsQ0FBQztZQUNoRCxDQUFDLENBQUMsQ0FBQztRQUNQLENBQUMsQ0FBQztRQUVNLFNBQUksR0FBbUIsQ0FDN0IsR0FBWSxFQUNaLEdBQWEsRUFDYixJQUFrQixFQUNRLEVBQUU7WUFDNUIsT0FBTyxnQkFBUyxDQUFDLFFBQVEsQ0FBQyxHQUFHLENBQUMsTUFBTSxDQUFDLEVBQUUsQ0FBQztpQkFDckMsSUFBSSxDQUFDLElBQUksQ0FBQyxFQUFFO2dCQUNYLE9BQU8sR0FBRyxDQUFDLE1BQU0sQ0FBQyxHQUFHLENBQUMsQ0FBQyxJQUFJLENBQUMsSUFBSSxDQUFDLENBQUM7WUFDcEMsQ0FBQyxDQUFDO2lCQUNELEtBQUssQ0FBQyxJQUFJLENBQUMsQ0FBQztRQUNqQixDQUFDLENBQUM7UUE5Q0EsSUFBSSxDQUFDLE9BQU8sR0FBRyxNQUFNLENBQUM7UUFDdEIsSUFBSSxDQUFDLE9BQU8sR0FBRyxnQkFBTSxFQUFFLENBQUM7UUFFeEIsSUFBSSxDQUFDLE9BQU8sQ0FBQyxJQUFJLENBQUMsR0FBRyxFQUFFLElBQUksQ0FBQyxPQUFPLENBQUMsQ0FBQztRQUNyQyxJQUFJLENBQUMsT0FBTyxDQUFDLEdBQUcsQ0FBQyxNQUFNLEVBQUUsSUFBSSxDQUFDLElBQUksQ0FBQyxDQUFDO0lBQ3RDLENBQUM7SUFHRCxNQUFNLENBQUMsU0FBUyxDQUFDLFNBQWM7UUFDN0IsSUFBSSxDQUFDLFFBQVEsS0FBSyxTQUFTO1lBQ3pCLENBQUMsQ0FBQyxDQUFDLElBQUksQ0FBQyxRQUFRLEdBQUcsSUFBSSxVQUFVLENBQUMsU0FBUyxDQUFDLENBQUM7WUFDN0MsQ0FBQyxDQUFDLENBQUMsSUFBSSxDQUFDLFFBQVEsR0FBRyxJQUFJLENBQUMsUUFBUSxDQUFDLENBQUM7UUFDcEMsT0FBTyxJQUFJLENBQUMsUUFBUSxDQUFDLE9BQU8sQ0FBQztJQUMvQixDQUFDO0NBa0NGO0FBRUQsa0JBQWUsQ0FBQyxNQUFjLEVBQVUsRUFBRTtJQUN4QyxPQUFPLFVBQVUsQ0FBQyxTQUFTLENBQUMsTUFBTSxDQUFDLENBQUM7QUFDdEMsQ0FBQyxDQUFDIn0=
SourceMaps.getMapForGeneratedPath: Finding SourceMap for /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/controllers/files.js by URI: data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiZmlsZXMuanMiLCJzb3VyY2VSb290IjoiIiwic291cmNlcyI6WyIuLi8uLi9zcmMvY29udHJvbGxlcnMvZmlsZXMudHMiXSwibmFtZXMiOltdLCJtYXBwaW5ncyI6Ijs7QUFBQSxxQ0FNaUI7QUFFakIseUNBQWlEO0FBR2pEO0lBS0UsWUFBWSxNQUFjO1FBa0JsQixZQUFPLEdBQW1CLENBQ2hDLEdBQVksRUFDWixHQUFhLEVBQ2IsSUFBa0IsRUFDQyxFQUFFO1lBQ3JCLElBQUksT0FBTyxHQUF1QixJQUFJLGdCQUFTLEVBQUUsQ0FBQztZQUNsRCxPQUFPLENBQUMsU0FBUyxHQUFHLElBQUksQ0FBQyxPQUFPLEdBQUcsR0FBRyxDQUFDLElBQUksQ0FBQyxTQUFTLENBQUM7WUFFdEQsT0FBTyxPQUFPO2lCQUNYLElBQUksRUFBRTtpQkFDTixJQUFJLENBQUMsQ0FBQyxrQkFBaUQsRUFBRSxFQUFFO2dCQUMxRCxPQUFPLEdBQUcsQ0FBQyxNQUFNLENBQUMsR0FBRyxDQUFDLENBQUMsSUFBSSxDQUFDLGtCQUFrQixDQUFDLENBQUM7WUFDbEQsQ0FBQyxDQUFDO2lCQUNELEtBQUssQ0FBQyxDQUFDLGdCQUFnQyxFQUFFLEVBQUU7Z0JBRTFDLE9BQU8sR0FBRyxDQUFDLE1BQU0sQ0FBQyxHQUFHLENBQUMsQ0FBQyxJQUFJLENBQUMsZ0JBQWdCLENBQUMsQ0FBQztZQUNoRCxDQUFDLENBQUMsQ0FBQztRQUNQLENBQUMsQ0FBQztRQUVNLFNBQUksR0FBbUIsQ0FDN0IsR0FBWSxFQUNaLEdBQWEsRUFDYixJQUFrQixFQUNRLEVBQUU7WUFDNUIsT0FBTyxnQkFBUyxDQUFDLFFBQVEsQ0FBQyxHQUFHLENBQUMsTUFBTSxDQUFDLEVBQUUsQ0FBQztpQkFDckMsSUFBSSxDQUFDLElBQUksQ0FBQyxFQUFFO2dCQUNYLE9BQU8sR0FBRyxDQUFDLE1BQU0sQ0FBQyxHQUFHLENBQUMsQ0FBQyxJQUFJLENBQUMsSUFBSSxDQUFDLENBQUM7WUFDcEMsQ0FBQyxDQUFDO2lCQUNELEtBQUssQ0FBQyxJQUFJLENBQUMsQ0FBQztRQUNqQixDQUFDLENBQUM7UUE5Q0EsSUFBSSxDQUFDLE9BQU8sR0FBRyxNQUFNLENBQUM7UUFDdEIsSUFBSSxDQUFDLE9BQU8sR0FBRyxnQkFBTSxFQUFFLENBQUM7UUFFeEIsSUFBSSxDQUFDLE9BQU8sQ0FBQyxJQUFJLENBQUMsR0FBRyxFQUFFLElBQUksQ0FBQyxPQUFPLENBQUMsQ0FBQztRQUNyQyxJQUFJLENBQUMsT0FBTyxDQUFDLEdBQUcsQ0FBQyxNQUFNLEVBQUUsSUFBSSxDQUFDLElBQUksQ0FBQyxDQUFDO0lBQ3RDLENBQUM7SUFHRCxNQUFNLENBQUMsU0FBUyxDQUFDLFNBQWM7UUFDN0IsSUFBSSxDQUFDLFFBQVEsS0FBSyxTQUFTO1lBQ3pCLENBQUMsQ0FBQyxDQUFDLElBQUksQ0FBQyxRQUFRLEdBQUcsSUFBSSxVQUFVLENBQUMsU0FBUyxDQUFDLENBQUM7WUFDN0MsQ0FBQyxDQUFDLENBQUMsSUFBSSxDQUFDLFFBQVEsR0FBRyxJQUFJLENBQUMsUUFBUSxDQUFDLENBQUM7UUFDcEMsT0FBTyxJQUFJLENBQUMsUUFBUSxDQUFDLE9BQU8sQ0FBQztJQUMvQixDQUFDO0NBa0NGO0FBRUQsa0JBQWUsQ0FBQyxNQUFjLEVBQVUsRUFBRTtJQUN4QyxPQUFPLFVBQVUsQ0FBQyxTQUFTLENBQUMsTUFBTSxDQUFDLENBQUM7QUFDdEMsQ0FBQyxDQUFDIn0=
SourceMaps.getMapForGeneratedPath: Using inlined sourcemap in /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/controllers/files.js
SourceMap: creating for /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/controllers/files.js
SourceMap: sourceRoot:
SourceMap: sources: ["../../src/controllers/files.ts"]
SourceMap: no sourceRoot specified, using script dirname: /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/controllers
SourceMaps: sourcemap url parsed from end of generated content: data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiZm9sZGVycy5qcyIsInNvdXJjZVJvb3QiOiIiLCJzb3VyY2VzIjpbIi4uLy4uL3NyYy9jb250cm9sbGVycy9mb2xkZXJzLnRzIl0sIm5hbWVzIjpbXSwibWFwcGluZ3MiOiI7O0FBQUEscUNBTWlCO0FBRWpCLDZDQUF1RDtBQUd2RDtJQUtFLFlBQVksTUFBYztRQWtCbEIsWUFBTyxHQUFtQixDQUNoQyxHQUFZLEVBQ1osR0FBYSxFQUNiLElBQWtCLEVBQ0MsRUFBRTtZQUNyQixJQUFJLFNBQVMsR0FBeUIsSUFBSSxvQkFBVyxFQUFFLENBQUM7WUFDeEQsU0FBUyxDQUFDLFdBQVcsR0FBRyxJQUFJLENBQUMsT0FBTyxHQUFHLEdBQUcsQ0FBQyxJQUFJLENBQUMsV0FBVyxDQUFDO1lBRTVELE9BQU8sU0FBUztpQkFDYixJQUFJLEVBQUU7aUJBQ04sSUFBSSxDQUFDLENBQUMsb0JBQXFELEVBQUUsRUFBRTtnQkFDOUQsT0FBTyxHQUFHLENBQUMsTUFBTSxDQUFDLEdBQUcsQ0FBQyxDQUFDLElBQUksQ0FBQyxvQkFBb0IsQ0FBQyxDQUFDO1lBQ3BELENBQUMsQ0FBQztpQkFDRCxLQUFLLENBQUMsQ0FBQyxrQkFBa0MsRUFBRSxFQUFFO2dCQUU1QyxPQUFPLEdBQUcsQ0FBQyxNQUFNLENBQUMsR0FBRyxDQUFDLENBQUMsSUFBSSxDQUFDLGtCQUFrQixDQUFDLENBQUM7WUFDbEQsQ0FBQyxDQUFDLENBQUM7UUFDUCxDQUFDLENBQUM7UUFFTSxTQUFJLEdBQW1CLENBQzdCLEdBQVksRUFDWixHQUFhLEVBQ2IsSUFBa0IsRUFDQyxFQUFFO1lBQ3JCLE9BQU8sb0JBQVcsQ0FBQyxJQUFJLENBQUM7Z0JBQ3RCLFdBQVcsRUFBRSxJQUFJLENBQUMsT0FBTyxHQUFHLEdBQUcsQ0FBQyxNQUFNLENBQUMsV0FBVzthQUNuRCxDQUFDO2lCQUNDLElBQUksQ0FBQyxNQUFNLENBQUMsRUFBRTtnQkFDYixPQUFPLEdBQUcsQ0FBQyxNQUFNLENBQUMsR0FBRyxDQUFDLENBQUMsSUFBSSxDQUFDLE1BQU0sQ0FBQyxDQUFDO1lBQ3RDLENBQUMsQ0FBQztpQkFDRCxLQUFLLENBQUMsR0FBRyxDQUFDLEVBQUU7Z0JBRVgsT0FBTyxHQUFHLENBQUMsTUFBTSxDQUFDLEdBQUcsQ0FBQyxDQUFDLElBQUksQ0FBQyxHQUFHLENBQUMsQ0FBQztZQUNuQyxDQUFDLENBQUMsQ0FBQztRQUNQLENBQUMsQ0FBQztRQW5EQSxJQUFJLENBQUMsT0FBTyxHQUFHLE1BQU0sQ0FBQztRQUN0QixJQUFJLENBQUMsT0FBTyxHQUFHLGdCQUFNLEVBQUUsQ0FBQztRQUV4QixJQUFJLENBQUMsT0FBTyxDQUFDLElBQUksQ0FBQyxHQUFHLEVBQUUsSUFBSSxDQUFDLE9BQU8sQ0FBQyxDQUFDO1FBQ3JDLElBQUksQ0FBQyxPQUFPLENBQUMsR0FBRyxDQUFDLGVBQWUsRUFBRSxJQUFJLENBQUMsSUFBSSxDQUFDLENBQUM7SUFDL0MsQ0FBQztJQUdELE1BQU0sQ0FBQyxTQUFTLENBQUMsU0FBYztRQUM3QixJQUFJLENBQUMsUUFBUSxLQUFLLFNBQVM7WUFDekIsQ0FBQyxDQUFDLENBQUMsSUFBSSxDQUFDLFFBQVEsR0FBRyxJQUFJLFlBQVksQ0FBQyxTQUFTLENBQUMsQ0FBQztZQUMvQyxDQUFDLENBQUMsQ0FBQyxJQUFJLENBQUMsUUFBUSxHQUFHLElBQUksQ0FBQyxRQUFRLENBQUMsQ0FBQztRQUNwQyxPQUFPLElBQUksQ0FBQyxRQUFRLENBQUMsT0FBTyxDQUFDO0lBQy9CLENBQUM7Q0F1Q0Y7QUFFRCxrQkFBZSxDQUFDLE1BQWMsRUFBVSxFQUFFO0lBQ3hDLE9BQU8sWUFBWSxDQUFDLFNBQVMsQ0FBQyxNQUFNLENBQUMsQ0FBQztBQUN4QyxDQUFDLENBQUMifQ==
SourceMaps.getMapForGeneratedPath: Finding SourceMap for /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/controllers/folders.js by URI: data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiZm9sZGVycy5qcyIsInNvdXJjZVJvb3QiOiIiLCJzb3VyY2VzIjpbIi4uLy4uL3NyYy9jb250cm9sbGVycy9mb2xkZXJzLnRzIl0sIm5hbWVzIjpbXSwibWFwcGluZ3MiOiI7O0FBQUEscUNBTWlCO0FBRWpCLDZDQUF1RDtBQUd2RDtJQUtFLFlBQVksTUFBYztRQWtCbEIsWUFBTyxHQUFtQixDQUNoQyxHQUFZLEVBQ1osR0FBYSxFQUNiLElBQWtCLEVBQ0MsRUFBRTtZQUNyQixJQUFJLFNBQVMsR0FBeUIsSUFBSSxvQkFBVyxFQUFFLENBQUM7WUFDeEQsU0FBUyxDQUFDLFdBQVcsR0FBRyxJQUFJLENBQUMsT0FBTyxHQUFHLEdBQUcsQ0FBQyxJQUFJLENBQUMsV0FBVyxDQUFDO1lBRTVELE9BQU8sU0FBUztpQkFDYixJQUFJLEVBQUU7aUJBQ04sSUFBSSxDQUFDLENBQUMsb0JBQXFELEVBQUUsRUFBRTtnQkFDOUQsT0FBTyxHQUFHLENBQUMsTUFBTSxDQUFDLEdBQUcsQ0FBQyxDQUFDLElBQUksQ0FBQyxvQkFBb0IsQ0FBQyxDQUFDO1lBQ3BELENBQUMsQ0FBQztpQkFDRCxLQUFLLENBQUMsQ0FBQyxrQkFBa0MsRUFBRSxFQUFFO2dCQUU1QyxPQUFPLEdBQUcsQ0FBQyxNQUFNLENBQUMsR0FBRyxDQUFDLENBQUMsSUFBSSxDQUFDLGtCQUFrQixDQUFDLENBQUM7WUFDbEQsQ0FBQyxDQUFDLENBQUM7UUFDUCxDQUFDLENBQUM7UUFFTSxTQUFJLEdBQW1CLENBQzdCLEdBQVksRUFDWixHQUFhLEVBQ2IsSUFBa0IsRUFDQyxFQUFFO1lBQ3JCLE9BQU8sb0JBQVcsQ0FBQyxJQUFJLENBQUM7Z0JBQ3RCLFdBQVcsRUFBRSxJQUFJLENBQUMsT0FBTyxHQUFHLEdBQUcsQ0FBQyxNQUFNLENBQUMsV0FBVzthQUNuRCxDQUFDO2lCQUNDLElBQUksQ0FBQyxNQUFNLENBQUMsRUFBRTtnQkFDYixPQUFPLEdBQUcsQ0FBQyxNQUFNLENBQUMsR0FBRyxDQUFDLENBQUMsSUFBSSxDQUFDLE1BQU0sQ0FBQyxDQUFDO1lBQ3RDLENBQUMsQ0FBQztpQkFDRCxLQUFLLENBQUMsR0FBRyxDQUFDLEVBQUU7Z0JBRVgsT0FBTyxHQUFHLENBQUMsTUFBTSxDQUFDLEdBQUcsQ0FBQyxDQUFDLElBQUksQ0FBQyxHQUFHLENBQUMsQ0FBQztZQUNuQyxDQUFDLENBQUMsQ0FBQztRQUNQLENBQUMsQ0FBQztRQW5EQSxJQUFJLENBQUMsT0FBTyxHQUFHLE1BQU0sQ0FBQztRQUN0QixJQUFJLENBQUMsT0FBTyxHQUFHLGdCQUFNLEVBQUUsQ0FBQztRQUV4QixJQUFJLENBQUMsT0FBTyxDQUFDLElBQUksQ0FBQyxHQUFHLEVBQUUsSUFBSSxDQUFDLE9BQU8sQ0FBQyxDQUFDO1FBQ3JDLElBQUksQ0FBQyxPQUFPLENBQUMsR0FBRyxDQUFDLGVBQWUsRUFBRSxJQUFJLENBQUMsSUFBSSxDQUFDLENBQUM7SUFDL0MsQ0FBQztJQUdELE1BQU0sQ0FBQyxTQUFTLENBQUMsU0FBYztRQUM3QixJQUFJLENBQUMsUUFBUSxLQUFLLFNBQVM7WUFDekIsQ0FBQyxDQUFDLENBQUMsSUFBSSxDQUFDLFFBQVEsR0FBRyxJQUFJLFlBQVksQ0FBQyxTQUFTLENBQUMsQ0FBQztZQUMvQyxDQUFDLENBQUMsQ0FBQyxJQUFJLENBQUMsUUFBUSxHQUFHLElBQUksQ0FBQyxRQUFRLENBQUMsQ0FBQztRQUNwQyxPQUFPLElBQUksQ0FBQyxRQUFRLENBQUMsT0FBTyxDQUFDO0lBQy9CLENBQUM7Q0F1Q0Y7QUFFRCxrQkFBZSxDQUFDLE1BQWMsRUFBVSxFQUFFO0lBQ3hDLE9BQU8sWUFBWSxDQUFDLFNBQVMsQ0FBQyxNQUFNLENBQUMsQ0FBQztBQUN4QyxDQUFDLENBQUMifQ==
SourceMaps.getMapForGeneratedPath: Using inlined sourcemap in /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/controllers/folders.js
SourceMap: creating for /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/controllers/folders.js
SourceMap: sourceRoot:
SourceMap: sources: ["../../src/controllers/folders.ts"]
SourceMap: no sourceRoot specified, using script dirname: /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/controllers
SourceMaps: sourcemap url parsed from end of generated content: data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiRmlsZS5qcyIsInNvdXJjZVJvb3QiOiIiLCJzb3VyY2VzIjpbIi4uLy4uL3NyYy9tb2RlbHMvRmlsZS50cyJdLCJuYW1lcyI6W10sIm1hcHBpbmdzIjoiOzs7Ozs7Ozs7OztBQUNBLHVFQUFtRTtBQUVuRSx5Q0FBcUU7QUFFckUsVUFBa0IsU0FBUSxxQkFBUztDQUdsQztBQURDO0lBREMsZ0JBQUksQ0FBQyxFQUFFLFFBQVEsRUFBRSxJQUFJLEVBQUUsQ0FBQzs7dUNBQ1A7QUFGcEIsb0JBR0M7QUFFRCxNQUFNLFNBQVMsR0FBb0IsSUFBSSxJQUFJLEVBQUUsQ0FBQyxnQkFBZ0IsQ0FBQyxJQUFJLEVBQUU7SUFDbkUsa0JBQWtCLEVBQUUsd0NBQWtCO0NBQ3ZDLENBQUMsQ0FBQztBQUVNLDhCQUFTIn0=
SourceMaps.getMapForGeneratedPath: Finding SourceMap for /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/models/File.js by URI: data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiRmlsZS5qcyIsInNvdXJjZVJvb3QiOiIiLCJzb3VyY2VzIjpbIi4uLy4uL3NyYy9tb2RlbHMvRmlsZS50cyJdLCJuYW1lcyI6W10sIm1hcHBpbmdzIjoiOzs7Ozs7Ozs7OztBQUNBLHVFQUFtRTtBQUVuRSx5Q0FBcUU7QUFFckUsVUFBa0IsU0FBUSxxQkFBUztDQUdsQztBQURDO0lBREMsZ0JBQUksQ0FBQyxFQUFFLFFBQVEsRUFBRSxJQUFJLEVBQUUsQ0FBQzs7dUNBQ1A7QUFGcEIsb0JBR0M7QUFFRCxNQUFNLFNBQVMsR0FBb0IsSUFBSSxJQUFJLEVBQUUsQ0FBQyxnQkFBZ0IsQ0FBQyxJQUFJLEVBQUU7SUFDbkUsa0JBQWtCLEVBQUUsd0NBQWtCO0NBQ3ZDLENBQUMsQ0FBQztBQUVNLDhCQUFTIn0=
SourceMaps.getMapForGeneratedPath: Using inlined sourcemap in /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/models/File.js
SourceMap: creating for /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/models/File.js
SourceMap: sourceRoot:
SourceMap: sources: ["../../src/models/File.ts"]
SourceMap: no sourceRoot specified, using script dirname: /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/models
SourceMaps: sourcemap url parsed from end of generated content: data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiRm9sZGVyLmpzIiwic291cmNlUm9vdCI6IiIsInNvdXJjZXMiOlsiLi4vLi4vc3JjL21vZGVscy9Gb2xkZXIudHMiXSwibmFtZXMiOltdLCJtYXBwaW5ncyI6Ijs7Ozs7Ozs7Ozs7QUFDQSx1RUFBbUU7QUFFbkUseUNBQXFFO0FBRXJFLFlBQW9CLFNBQVEscUJBQVM7Q0FHcEM7QUFEQztJQURDLGdCQUFJLENBQUMsRUFBRSxRQUFRLEVBQUUsSUFBSSxFQUFFLE1BQU0sRUFBRSxJQUFJLEVBQUUsQ0FBQzs7MkNBQ25CO0FBRnRCLHdCQUdDO0FBRUQsTUFBTSxXQUFXLEdBQXNCLElBQUksTUFBTSxFQUFFLENBQUMsZ0JBQWdCLENBQUMsTUFBTSxFQUFFO0lBQzNFLGtCQUFrQixFQUFFLHdDQUFrQjtDQUN2QyxDQUFDLENBQUM7QUFFTSxrQ0FBVyJ9
SourceMaps.getMapForGeneratedPath: Finding SourceMap for /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/models/Folder.js by URI: data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiRm9sZGVyLmpzIiwic291cmNlUm9vdCI6IiIsInNvdXJjZXMiOlsiLi4vLi4vc3JjL21vZGVscy9Gb2xkZXIudHMiXSwibmFtZXMiOltdLCJtYXBwaW5ncyI6Ijs7Ozs7Ozs7Ozs7QUFDQSx1RUFBbUU7QUFFbkUseUNBQXFFO0FBRXJFLFlBQW9CLFNBQVEscUJBQVM7Q0FHcEM7QUFEQztJQURDLGdCQUFJLENBQUMsRUFBRSxRQUFRLEVBQUUsSUFBSSxFQUFFLE1BQU0sRUFBRSxJQUFJLEVBQUUsQ0FBQzs7MkNBQ25CO0FBRnRCLHdCQUdDO0FBRUQsTUFBTSxXQUFXLEdBQXNCLElBQUksTUFBTSxFQUFFLENBQUMsZ0JBQWdCLENBQUMsTUFBTSxFQUFFO0lBQzNFLGtCQUFrQixFQUFFLHdDQUFrQjtDQUN2QyxDQUFDLENBQUM7QUFFTSxrQ0FBVyJ9
SourceMaps.getMapForGeneratedPath: Using inlined sourcemap in /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/models/Folder.js
SourceMap: creating for /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/models/Folder.js
SourceMap: sourceRoot:
SourceMap: sources: ["../../src/models/Folder.ts"]
SourceMap: no sourceRoot specified, using script dirname: /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/models
SourceMaps: sourcemap url parsed from end of generated content: data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoic2VydmVyLmpzIiwic291cmNlUm9vdCI6IiIsInNvdXJjZXMiOlsiLi4vc3JjL3NlcnZlci50cyJdLCJuYW1lcyI6W10sIm1hcHBpbmdzIjoiOztBQUVBLCtCQUE0QjtBQUM1QixNQUFNLElBQUksR0FBUSxPQUFPLENBQUMsR0FBRyxDQUFDLHlCQUF5QixJQUFJLElBQUksQ0FBQztBQUNoRSxPQUFPLENBQUMsR0FBRyxDQUFDLHVCQUF1QixFQUFFLE9BQU8sQ0FBQyxHQUFHLENBQUMsUUFBUSxDQUFDLENBQUM7QUFFM0QsU0FBRyxDQUFDLE1BQU0sQ0FBQyxJQUFJLEVBQUUsQ0FBQyxHQUFRLEVBQUUsRUFBRTtJQUM1QixJQUFJLEdBQUcsRUFBRTtRQUNQLE9BQU8sT0FBTyxDQUFDLEdBQUcsQ0FBQyxHQUFHLENBQUMsQ0FBQztLQUN6QjtJQUNELE9BQU8sT0FBTyxDQUFDLEdBQUcsQ0FBQyx3Q0FBd0MsSUFBSSxFQUFFLENBQUMsQ0FBQztBQUNyRSxDQUFDLENBQUMsQ0FBQyJ9
SourceMaps.getMapForGeneratedPath: Finding SourceMap for /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/server.js by URI: data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoic2VydmVyLmpzIiwic291cmNlUm9vdCI6IiIsInNvdXJjZXMiOlsiLi4vc3JjL3NlcnZlci50cyJdLCJuYW1lcyI6W10sIm1hcHBpbmdzIjoiOztBQUVBLCtCQUE0QjtBQUM1QixNQUFNLElBQUksR0FBUSxPQUFPLENBQUMsR0FBRyxDQUFDLHlCQUF5QixJQUFJLElBQUksQ0FBQztBQUNoRSxPQUFPLENBQUMsR0FBRyxDQUFDLHVCQUF1QixFQUFFLE9BQU8sQ0FBQyxHQUFHLENBQUMsUUFBUSxDQUFDLENBQUM7QUFFM0QsU0FBRyxDQUFDLE1BQU0sQ0FBQyxJQUFJLEVBQUUsQ0FBQyxHQUFRLEVBQUUsRUFBRTtJQUM1QixJQUFJLEdBQUcsRUFBRTtRQUNQLE9BQU8sT0FBTyxDQUFDLEdBQUcsQ0FBQyxHQUFHLENBQUMsQ0FBQztLQUN6QjtJQUNELE9BQU8sT0FBTyxDQUFDLEdBQUcsQ0FBQyx3Q0FBd0MsSUFBSSxFQUFFLENBQUMsQ0FBQztBQUNyRSxDQUFDLENBQUMsQ0FBQyJ9
SourceMaps.getMapForGeneratedPath: Using inlined sourcemap in /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/server.js
SourceMap: creating for /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist/server.js
SourceMap: sourceRoot:
SourceMap: sources: ["../src/server.ts"]
SourceMap: no sourceRoot specified, using script dirname: /Users/bbendavi/Documents/docker_typescript_debug_vscode/dist
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
Discovering targets via http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up
To client: {"seq":0,"type":"event","event":"output","body":{"category":"telemetry","output":"ClientRequest/attach","data":{"Versions.DebugAdapterCore":"4.2.2","Versions.DebugAdapter":"1.23.5","successful":"false","exceptionType":"firstChance","exceptionMessage":"Cannot connect to runtime process, timeout after {_timeout} ms - (reason: {_error}).","exceptionName":"Error","exceptionStack":"Error: Cannot connect to runtime process, timeout after {_timeout} ms - (reason: {_error}).\n    at Object.runtimeConnectionTimeout (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/ms-vscode.node-debug2/node_modules/vscode-chrome-debug-core/out/src/errors.js:91:12)\n    at utils.retryAsync.catch.err (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/ms-vscode.node-debug2/node_modules/vscode-chrome-debug-core/out/src/chrome/chromeConnection.js:100:49)\n    at \n    at process._tickCallback (internal/process/next_tick.js:109:7)","exceptionId":"2010","timeTakenInMilliseconds":"9982.722306","requestType":"request"}}}
To client: {"seq":0,"type":"response","request_seq":2,"command":"attach","success":false,"message":"Cannot connect to runtime process, timeout after 10000 ms - (reason: Cannot connect to the target: socket hang up).","body":{"error":{"id":2010,"format":"Cannot connect to runtime process, timeout after {_timeout} ms - (reason: {_error}).","variables":{"_error":"Cannot connect to the target: socket hang up","_timeout":"10000"}}}}
From client: disconnect({"restart":false})
To client: {"seq":0,"type":"event","event":"output","body":{"category":"telemetry","output":"report-start-up-timings","data":{"Versions.DebugAdapterCore":"4.2.2","Versions.DebugAdapter":"1.23.5","RequestedContentWasDetected":"false","Steps":"["BeforeFirstStep","ClientRequest/initialize","ClientRequest/attach","Attach","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation","Attach.RequestDebuggerTargetsInformation"]","All":"10005.326405","BeforeFirstStep":"[12.56266]","WaitingAfter.ClientRequest/initialize":"[15.666987]","ClientRequest/initialize":"[5.022744]","ClientRequest/attach":"[7.334406]","Attach":"[1.154245]","Attach.RequestDebuggerTargetsInformation":"[221.658954,208.47828,205.174857,207.489076,207.042777,208.197304,207.18647,207.862787,203.765369,208.735595,208.527577,203.700679,207.933444,207.316369,206.450237,208.09298,209.419296,206.715585,204.158625,207.3442,206.211928,213.567018,209.404862,215.604441,206.089368,207.79625,209.735247,207.430767,204.231206,208.303598,208.089151,204.942955,209.747735,207.265858,204.505154,205.224522,204.433681,207.198089,206.579608,205.840778,205.231675,206.638845,208.983487,209.955565,208.875781,208.578899,203.639692,208.877645,10.107002]","WaitingAfter.ClientRequest/attach":"[10000.384164]","RequestedContentWasNotDetectedReason":"shutdown"}}}
Terminated: Got disconnect request
Waiting for any pending steps or log messages.
To client: {"seq":0,"type":"response","request_seq":3,"command":"disconnect","success":true}
Current step and log messages complete
To client: {"seq":0,"type":"event","event":"output","body":{"category":"telemetry","output":"debugStopped","data":{"Versions.DebugAdapterCore":"4.2.2","Versions.DebugAdapter":"1.23.5","reason":"Got disconnect request"}}}
To client: {"seq":0,"type":"event","event":"terminated"}
To client: {"seq":0,"type":"event","event":"output","body":{"category":"telemetry","output":"ClientRequest/disconnect","data":{"Versions.DebugAdapterCore":"4.2.2","Versions.DebugAdapter":"1.23.5","successful":"true","timeTakenInMilliseconds":"2.163995","requestType":"request"}}}
BBENDAVI-M-D0S5:docker_typescript_debug_vscode bbendavi$

Our debugger can't connect to your Node instance running on http://localhost:9225/json/list
HTTP GET failed: Error: socket hang up`

Can you to start your Docker container (looks like it's done via npm run docker-compose-debug, and see if you can access http://localhost:9225/json/list from your browser?
That needs to get working first, before VS Code can connect it's debugger to it.

I can't
But I see this output:
docker-ts-debug    | Debugger listening on ws://127.0.0.1:9225/221b24e1-01e3-4830-ae73-db15a2485006
and I can hit my server's API's when running in Docker.
When I use the launch configuration "npm-nodemon" (not in docker) the debugger works fine
Can you clone my project and try it locally?
I basically followed the recipe.
https://github.com/barakbd/docker_typescript_debug_vscode

I'm no Docker expert, so I'm not too much help. You need to get port 9225 properly forwarded from your Docker container. That seems to be your root cause. There's probably many guides on how to get that working.

According to my docker-compose it is open.

I also inspect the running container and the port is mapped correctly.
Is there anyone there (maybe the person who wrote the recipe) that could look at my demo project?
https://github.com/barakbd/docker_typescript_debug_vscode
Much appreciated!

Got it to work. Recipe needs to be updated.
You can see my project for updates.

Mainly for MacOS:
nodemon:
use address 0.0.0.0, e.g.:
-inspect=0.0.0.0:9229
luanch.json:
include dist folder in the paths, e.g.:
"localRoot": "${workspaceFolder}/dist",
"remoteRoot": "/server/dist",

authors: auchenberg barakbd

repo: Microsoft/vscode-recipes


text:
Can't set variable to object

Edit a variable and set its value to [1,2,3] or anything else that resolves to an object, and there's an error returned. Seems to handle primitives but not objects.
see https://github.com/Microsoft/vscode-node-debug/issues/91

@isidorn I've added the ´variablesReference´, ´namedVariables´, ´indexedVariables´ to the ´SetVariableResponse´ so that you can propagate them properly.

source: gharchive/issue

repo: Microsoft/vscode

license: MIT

license_type: permissive

license_source: github-api


text:
Debugger and runTimeArgs order

VSCode Version: 1.7.2
OS Version: macos 10.12.1

I don't have nodejs installed locally on my machine, but I'm using the official docker image to run the typescript. I tried to setup VS Code to launch the docker image but the --debug-brk flag is injected before any of the arguments. Is there any way I could control the order of the arguments?
Steps to Reproduce:

Use the following launch.json:

{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "node",
      "request": "launch",
      "name": "Launch Program",
      "program": "${workspaceRoot}/index.ts",
      "cwd": "${workspaceRoot}",
      "outFiles": [],
      "sourceMaps": true,
      "env": {
        "NODE_ENV": "development"
      },
      "outDir": "${workspaceRoot}/bin",
      "runtimeExecutable": "docker",
      "runtimeArgs": ["run", "-ti", "node:6.9.1"]
    }
  ]
}

Run the program in debug mode.

The console prints:
docker --debug-brk=35420 run -ti node:6.9.1 bin/index.js
flag provided but not defined: --debug-brk
See 'docker --help'.

To run the application in docker that line should read instead:
docker run -ti node:6.9.1 bin/index.js --debug-brk=35420

@danielepolencic you can avoid that VS Code passes a --debug-brk=nnnnn to the runtime by managing the debug port manually. Just set a "port": 55555 attribute in your launch config and add a corresponding runtime argument "--debug-brk=55555".
And please use outFiles correctly instead of the deprecated outDir:
{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "node",
      "request": "launch",
      "name": "Launch Program",
      "program": "${workspaceRoot}/index.ts",
      "cwd": "${workspaceRoot}",
      "outFiles": [ "${workspaceRoot}/bin/**/*.js" ],
      "sourceMaps": true,
      "env": {
        "NODE_ENV": "development"
      },
      "port": 35420,
      "runtimeExecutable": "docker",
      "runtimeArgs": ["run", "-ti", "node:6.9.1", "--debug-brk=35420" ]
    }
  ]
}

@weinand, sorry for commenting on an old issue, but I just ran into a similar problem while trying to get VS Code to collaborate with nvm, and I've come to believe that this issue shouldn't have been closed.
I got it to work using your workaround:
{
  "version": "0.2.0",
  "configurations": [
    {
      "protocol": "inspector",
      "type": "node",
      "request": "launch",
      "name": "Mocha Tests",
      "program": "${workspaceFolder}/node_modules/mocha/bin/_mocha",
      // Hardwire the port to prevent VS from injecting --inspect-brk=... before the runtimeArgs:
      // https://github.com/Microsoft/vscode/issues/16173#issuecomment-263496120
      "port": 49534,
      "args": [
        "-u", "tdd",
        "--timeout", "999999",
        // ...
        "tests/**/*.js"
      ],
      "internalConsoleOptions": "openOnSessionStart",
      "runtimeExecutable": "${env:NVM_DIR}/nvm-exec",
      "runtimeArgs": [
        "node",
        "--inspect-brk=49534" // Has to match the "port" config above
      ]
    }
  ]
}

It would have been nicer if I could just have omitted the "port": 49534 config and the hardcoded --inspect-brk=49534, but if I do that, a non-functional command line is generated, similar to the Docker problem mentioned above:
/Users/andreaslind/.nvm/nvm-exec --inspect=41943 --debug-brk node node_modules/mocha/bin/_mocha -u tdd --timeout 999999 ... tests/**/*.js

... the problem being that node (from runtimeArgs) should come right after /Users/andreaslind/.nvm/nvm-exec.
It seems unintuitive that Code would inject that before the runtimeArgs, and now we have two examples of it causing undesirable results. Don't you agree that it seems like an actual bug?

@papandreou Wouldn't you setting your default Node version via NVM solve things and simplify the configuration? https://eric.blog/2016/08/23/set-default-node-version-with-nvm/

Hey @auchenberg, long time no see :). I have specified the default alias, but I’m working on several projects, and they’re not all ready to upgrade node at the same time. I think it’s very common for applications (rather than libs) to be tied to a single major version of node at any given time. Upgrading will usually require you to upgrade several dependencies, some of which won’t be backwards compatible with the old node version. Also, you’ll quickly start to use new language features that weren’t available in the old version.
Because of that, it’s practical to have local .nvmrc files version controlled with the individual projects. For the lack of something better, .nvmrc checked in at the root seems to have become the standard way of declaring the node version, as you can also tell from the number of people weighing in here and here
As another example, Travis supports .nvmrc directly: https://docs.travis-ci.com/user/languages/javascript-with-nodejs/#Specifying-Node.js-versions-using-.nvmrc

@roblourens For the legacy protocol I'm now adding the --debug... flag after all runtimeArgs (instead of before). You might want to do the same for the --inspect... flag for the inspector protocol.

Done!

Wow, thanks, guys :)

Verification:
create a launch config that has both runtime args and program args, then verify that the "--debug" or "--inspect" argument comes at the end of the runtime args before the program args.
Verify this for both protocols.

authors: auchenberg danielepolencic papandreou roblourens weinand


text:
Custom CompletionItemProvider's results get deleted

VSCode Version:
1.8.0-insider (tested for 1.7, too)
OS Version:
Windows 10

Steps to Reproduce:

Created following CompletionItemProvider:

export class ManifestCompletionItemProvider implements vscode.CompletionItemProvider {
    public provideCompletionItems(document: vscode.TextDocument, position: vscode.Position, token: vscode.CancellationToken): Thenable<vscode.CompletionItem[]> | vscode.CompletionItem[]  {
		let line = document.lineAt(position);
		let matches = line.text.match(/"(.*)"\s*:\s*(.*)\s*[,]?\s*/)
		if(!matches)
			return [];

		let key = matches[1];
		let value = matches[2];
		let val;

		switch (key) {
			case "target":
				console.log("Target triggered");
				let targets: string[];
				try {
					let targets = getTargets(JSON.parse(document.getText()));
				} catch (error) {
					return [];
				}

				if(!targets)
					return [];
				value = value.match(/"(.*)"/)[1];

				if(!value) {
					val = enumerable.asEnumerable(targets).Select(x => {
						let item = new vscode.CompletionItem(x, vscode.CompletionItemKind.Text);
						item.insertText = "\""+x+"\"";
						return item;
					}).ToArray();
					return val;
				}
				return enumerable.asEnumerable(targets).Where(x => x.toLowerCase().startsWith(value.toLowerCase())).Select(x => {
						let item = new vscode.CompletionItem(x, vscode.CompletionItemKind.Text);
						item.insertText = "\""+x+"\"";
						return item;
					}).ToArray();
			default:
				return [];
		}
    }
}

I added it to the json language server completion providers:

const ui5_manifest: vscode.DocumentFilter = { language: "json", scheme: 'file', pattern: "**/manifest.json"};
context.subscriptions.push(vscode.languages.registerCompletionItemProvider(ui5_manifest, new ManifestCompletionItemProvider));

When I trigger it by changing pressing ctrl+space my breakpoint gets hit, my method runs properly and returns the array of CompletionItems. For the first time (sometimes) the results show up, but vanish immediately after that and never show up again.

I can trigger the method multiple times and it always returns that array, but no code completion.
Is there any way to convince the JSON Completion to show my results, too?
The document filter should get a high priority, as I filled in all props.
And why is it crashing the whole list. There should be the completion items from the JSON language server?

Hello,
I figured it out myself. I did two things:

caught all errors and returned empty arrays
made it async using promise.

Is there some kind of timeout, if the method takes too long?


text:
Allow to configure title bar information

It would be great if we could configure the information that gets displayed in the title bar. I use ManicTime a lot, and it's hard to auto tag my activities when the title bar basically only displays the file name and root folder name. Having the full path to the file and the git branch name would be super helpful.
For some other ideas, this VS plugin is super rad and affords complete control over what gets displayed in the title bar. https://visualstudiogallery.msdn.microsoft.com/2e8ebfe4-023f-4c4d-9b7a-d05bbc5cb239

@bpasero By assigning this to yourself, does that mean it might happen? If so, please let me know if you would like some help, even if it's just for feedback.

This issue is currently assigned to the backlog. Every sprint we pick items from the backlog to plan for the current iteration. Please see https://github.com/Microsoft/vscode/wiki/Issue-Tracking#planning

+1. The more I use VS Code on bigger projects, it's becoming frustrating to be unable to distinguish between open windows.  I wish I could configure the title to just show [Root Folder] - [File], since it's hard to distinguish between open projects when the file name is shown first. But some simple templating system would probably solve everyone's problem.

https://github.com/Microsoft/vscode/issues/12625 for the issue to show the full path in the title bar. This might resolve many (but not all) concerns of this issue.

@bpasero i do appreciate the effort but actually this still does not address the issue (at least as far as Windows) is concerned. It may actually make it worse (though since it's an option that's not an issue).
The problem is that in Windows, the taskbar shows a preview of all windows  for a given application, and there is only limited space to show the title. Showing the full path would give me exactly the opposite problem I have now: I'd just see the part of the path, starting with the root, that fits in the display. So with this enabled, I'd most likely have no information at all about which window was which, since they likely all share a common root path.
What is really needed is the ability to show project-root/../filename. The parent folder is nearly always the identifying feature for a project. I don't even care if the filename gets cut off- because I really just want to be able to determine which project is open from the title bar.

@jamietre we can still tweak this experience and I welcome the problem description you gave, though I am not sure how to best solve it.
Here is how your scenario looks like without the new option enabled:

And here with the option turned on:

This makes it hard to see the currently opened file but you can easily see the full path when you compare the 2 window titles in full (not from this experience).
I think this feature request is still valid for that particular scenario because you could then really compose the title you want, I am not sure we should change the experience by default with the new option.
I am open for suggestions though if the default experience when this new option is turned on should be changed.

Thanks for all the feedback, it's very appreciated.
In my case almost all my code is under a single heirarchy like d:/users/jtreworgy/code/... -- so if I were lucky I might get a few characters of the root folder. But I also work in subfolders with groups of projects, too, so it would be quite realistic for there to be nothing unique at all. I could try to keep everything under shallow heirarchies but I guess I'd rather not have to design my file system architecture around accomodating VS Code ;)
The perfect world for me would be the ability to pass a template like "{rootFolder} - {fileName}" instead of boolean options for predefined templates. Just having rootFolder, fileName and fullPath as available parameters would accomodate everything that's been discussed here as well as the current state.
Even more perfect world, the ability to invoke a  javascript function that I wrote to return my title given the path as input :) but then I've written a plugin haven't I..

@jamietre but how is root folder solving it when you have 2 workspaces with the same name in different hierarchies?
"{rootFolder} - {fileName}" isn't that what we are showing today without the full path option enabled?

I wasn't considering that possibility - I would never have two workspaces with the same name open (or at least, it's not particularly likely, maybe if I was trying to deep dive some comparison between two branches?). But that's not my problem generally... if that is an issue for some people, perhaps a possible solution is to also display a numerical index  identifying which was opened first? Can VS code instances know anything about each other?
But anyway -- right now the problem is the root folder appears last, e.g. {fileName} - {rootFolder} so it is cut off for long file names (which are pretty common in our projects). And it's hard to parse them even if they are visble when they aren't left-aligned.

Oh yeah, that is true. I was not thinking about the fact that the file name comes first. We cannot change that without making it hard for users that want to quickly glance at the file name in that scenario so I guess no matter what it boils down to making it configurable if any.
I still think the setting to show a full path is a good one, so I will keep it as is for now and we leave this one here open.

I would really love to hve an option/config to at least show {rootFolder} first. event if its just that (don't really see the point of having the filename in the title bar. For me the next most useful information would be the git branch name: "{rootFolder} - {branchName}"

@Cedric-Venet agreed. If VS Code allowed you to drag a file out to start a new window, I could see how that might be useful to some. But you can't -- so it just doesn't seem likely that's what many people are looking for a file name when trying to discriminate between open instances.
I looked at the code that creates the window template it vs/workbench/services/history/browser/history.ts... it seems straightforward and I am sure I could handle the change to support user-provided templates if this change would be accepted. Would you be interested in a PR? I have no idea what the overhead is in getting set up to create vs code builds - if you can convince me it's not too bad I'm willing to take a shot :)

@jamietre Dunno if this exactly deals with one of your use cases, but there's a plugin called "Open Folder Context Menus for VS Code" that "Quickly opens a new instance of VS Code from the Explorer". Works pretty well for me.

@alexdresko the problem isn't opening VSCode, it's finding the correct instance among a bunch of already opened ones.

I often have multiple windows of VSCode open. Until I found this issue I'd had a different thought on how to solve it: setting a workspace/folder colour.
I commonly have two or more windows open, and sometimes one using the integrated debugging feature for a backend written in NodeJs.  The bottom bar goes orange when debugging, and I've been using that help distinguish which is which.
You can see this in a picture already posted in this thread:

I tend to switch between full-screen windows using the keyboard, rather than hovering on the taskbar to select a window. But even when flicking between full-screen windows, it's not always clear where you've switched to. And while being able to customise the title of the window would give me somewhere to glance at, I think that colourising some part of the window would allow for even quicker discerning of which instance has been focused.
Although the title of this issue is "Allow to configure title bar information" I figured that my suggestion probably belonged here at first rather than in it's own issue, since the other comments here have equated this issue to "Allow to configure easy distinction between open windows". But I can create a new issue if others agree with my suggestion but don't want to lump the two together.

+1. I frequently work on multiple sub-projects of a large project at the same time. {filename} - {root folder} doesn't help because, for other reasons, all of my root folders are 'src' in VSCode for each of my projects.

The ability to configure the window title to show "{rootFolder} - {fileName}" or even better  just "{rootFolder}" instead of "{fileName} - {rootFolder}" is critical for us. We're working in a multiple project setup in Windows and it is currently impossible to distinguish open vscode windows on the taskbar.
This seems to be a rather trivial configuration option to implement, but it adds tremendous usability value.

From the discussion I can see the following template variables as being considered useful:

{activeFileName}: e.g. myFile.txt
{activeFilePath}: e.g. /Users/Development/myProject/myFile.txt
{workspaceName}: e.g. myProject
{workspacePath}: e.g. /Users/Development/myProject
{appName}: e.g. VS Code

(the current git branch is not straight forward to add for layering issues but maybe later)
There is still something not clear to me: We will probably soon support multiple root folders per workspace. In that case {workspaceName} or {workspacePath} do not make much sense. If I had the folders myProject and otherProject open in the same window, I would probably expect the title to show me myProject, otherProject. In that case, showing the full path of both does not make much sense either. Maybe instead of {workspaceName} it should rather be called {projectName}. {workspacePath} could be {projectPath} and be somehow smartly computed from the root folders (however that works...).

I think of workspaces as more of a conceptual entity - like how I can have a VS .SLN with a name that is completely different from the containing folder. If you're going to allow multiple folders, you're essentially creating something similar to a VS .SLN, right? That workspace name is something we'd want to add to the title bar, as we as, separately, the path to the workspace file. At that point, the folders in the workspace don't really matter. I don't expect VS to show me the path to all of the projects in the .SLN in the title bar. The name and path to the currently open file are important though.

I settled on the following solution: there is a new setting window.title (the previous window.showFullPath is no longer supported) that allows to configure the title based on some variables.
Variables are declared using $() syntax and the following are available:

$(activeEditorName): e.g. myFile.txt
$(activeFilePath): e.g. /Users/Development/myProject/myFile.txt
$(rootName): e.g. myProject
$(rootPath): e.g. /Users/Development/myProject
$(appName): e.g. VS Code
$(dirty): a dirty indicator if the active editor is dirty
$(separator): a conditional separator (" - ") that only shows when surrounded by variables with values

Default values on the various OS:
macOS:
$(activeEditorName)$(separator)$(rootName)
Linux/Windows:
$(dirty)$(activeEditorName)$(separator)$(rootName)$(separator)$(appName)

Is this in the latest insiders build?

@alexdresko it will be tomorrow. I did a slight update to let the variables be ${} instead of $().
Happy for everyones feedback once this is out.

w00t!!!!

Yeah, I can see how a scripted solution would be better, but let's see how far we get with this approach for now.

It would really just be a more universal solution to this kind of thing, generally, but I assume it involves some kind of infrastructure change or new convention, since config is json & not js.
Really just threw that out there for long-term consideration. I'm very happy with the way this is working.

Actually I wonder if ${separator} should be dropped, it seems there is really only one usecase for it: to separate between 2 variables if (and only if) both variables are present:
${foo}{separator}${bar}
Why not just automatically add a separator if there is ${foo}${bar}? Makes it easier to read and gets rid of a complicated and confusing variable.

You might not always want it, e.g. ${dirty}${foo}

Hm yeah 💩

Thanks, I've been waiting for this for long time.
Small changes sometime make a big difference :)
On Tue, Feb 7, 2017 at 7:16 PM, Benjamin Pasero notifications@github.com
wrote:

Hm yeah 💩
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/1723#issuecomment-278070672,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARwKKPmdVfRcuBt8wcpa48vJriFMafleks5raKcEgaJpZM4G9Nhu
.

I really like it.  Thank you for this update.
You might want to think about allowing people to add parsing logic (too much?)
In my case, our code is laid out like:
/path/to/project/[Branch Name]
So, using {rootPath} is nice, but I'd like to trim "[Branch Name]" off most of the time.
It might be a bit much to support this though

This doesn't seem to be working for me.  I'm not seeing the file name first.. just seeing
"C:\Path\To\Project - Visual Studio Code - Insiders"
"window.title": "${dirty}${activeEditorName}${separator}${rootPath}${separator}${appName}",

I restarted the app and opened various files.
Also, does it require a restart to work?  Kind of hard to test what you're doing that way

Pro tip: You won't see the setting changes when editing the settings file. You have to switch to another file in your workspace to see the changes you've made in the settings. Not sure why that is exactly.

I'm still doing that and it's not happening :(

The tooltip help for it isn't formatting properly either :)
Should I open a bug?

Huh.. I think it's actually updating, but taking a LONG time to do so on this machine.  So, I think my problem with the title bar is not a problem.

Hmm.. now we just need this feature for the "recent window" list, which just shows the folder name for me, which isn't specific enough (lots of "main" listed in there)

Small update, I added ${activeFilePathRelative} to be able to show a shorter path to the active opened file if the file is from within the workspace opened. E.g. instead of /Users/Development/myProject/myFolder/myFile.txt showing myFolder/myFile.txt if myFolder is opened. Together with ${rootName} this allows to show a file path as myProject/myFolder/myFile.txt if desired.

Another update after feedback from testing during this week from the team: ${activeFilePath} and ${activeFilePathRelative} are working only if a file is opened, making the configuration of the window.title hard when non-file editors are opened.
I decided to revisit the variables around file paths and change them because things are getting complicated when an editor is not showing a file.
Here is my new solution:

${activeEditorLong}: e.g. /Users/Development/myProject/myFolder/myFile.txt
${activeEditorMedium}: e.g. myFolder/myFile.txt
${activeEditorShort}: e.g. myFile.txt

If there is no long editor label, the medium one will be used. And the same is true for medium and short.
Basically:

replace ${activeFilePath} with ${activeEditorLong}
replace ${activeFilePathRelative} with ${activeEditorMedium}

I hope this works for everyone, should be available in today's insider build.

@bpasero is there a way to remove the [Unsupported] suffix in the title, when vscode has a modified installation (Using custom CSS)?

No, we strongly advice against using extensions that modify our bits so it is in the best interest to show this not only to you as a user but also to us when we have to investigate bugs which are caused by extensions that patch our bits.

@bpasero "window.title" is a neat addition. Can we have something similar for tabs?

I'd love to see the last directory name as a prefix to the filename on all tabs.
Vim tabs are very smart about tab names btw.

Yeah this was reported already as feature request.

I made a quick extension for setting the title for the workspace: https://marketplace.visualstudio.com/items?itemName=nilpatel.title
Those who find this thread may find it useful.

@nileshp87 works great, thank you!

authors: Cedric-Venet VojtechVitek alexdresko bpasero chief1ic gilboa23 jamietre nfour nileshp87 saborrie tommck


text:
Feature Request: I am using cucumber protractor for navigate cucumber to step definition

Feature Request
I am not able to navigate to another method from feature file.
scenario:
I have cucumber features in my feature file id i click or cont+click or double click this should not take to that method.
#cucumber #javascript #featurefile

@harigowtham91 can you share what cucumber features is?

Given that he mentioned Protractor, "cucumber features" are almost certainly .feature files as described here: https://cucumber.io/docs/reference
See also https://github.com/cucumber/cucumber-js and https://github.com/AndrewKeig/protractor-cucumber

We do not provide cucumber support out of the box. Please try filing this feature request against one of the cucumber extensions: https://marketplace.visualstudio.com/search?term=cucumber&target=VSCode&category=All categories&sortBy=Relevance

authors: bpasero harigowtham91 mjbvz rmunn


text:
Not detecting env PATH changes made after a VScode instance has been opened

VSCode Version: Code 1.9.0 (27240e71ef390bf2d66307e677c2a333cebf75af, 2017-02-02T08:31:00.827Z)
OS Version: Windows_NT ia32 10.0.14393
Extensions:

Extension
Author
Version

python
donjayamanne
0.5.8

live-html-previewer
hdg
0.0.1

latex-workshop
James-Yu
0.2.13

cpptools
ms-vscode
0.10.0

latex
ms-vscode
0.1.3

code-spell-checker
streetsidesoftware
0.17.2

vim
vscodevim
0.5.2

Steps to Reproduce:

open an instance of VScode
change the PATH environment variable
reload VScode observe inability to detect the new PATH changes.

Fixes:
a) load the integrated terminal (powershell) and reset the system the local PATH variable to that of the system i.e. thanks stackoverflow
$env:Path = [System.Environment]::GetEnvironmentVariable("Path","Machine") + ";" + System.Environment]::GetEnvironmentVariable("Path","User")

This is only temporary - if i close all instances and then restart VScode then the path variable reverts to the out of date version... going to try Fixes b.
b) Reboot - (hypothesised as this would reseed all processes with the system envs)
Context:
This was encountered by updating my MiKTeX installation after installing a the latex-workshop extension. I rebooted VScode and noticed that it couldn't detect any pdflatex binary in the PATH variable, loading up an external console I verified that it was accessible. So I killed all VScode windows (I had a second instance open) and reopened and was presented by the same error. Finally I opened up the integrated console in VScode and saw that it had the old PATH env variable so applied Fixes a).
Is it possible there is some persistent console or background process that is hanging on to the out of date?

yup fixes b works

This looks like it just overrides the PATH environment in your local environment, not globally (@daviwil?).
$env:Path = [System.Environment]::GetEnvironmentVariable("Path","Machine") + ";" + System.Environment]::GetEnvironmentVariable("Path","User")

If this is the case then this behavior is expected.
Here's how the environment works in VS Code and the terminal:

All VS Code windows share the environment of the first (the main process), you need to close all windows to refresh the environment.
The terminal environment is inherited (cloned) from the VS Code window, meaning any changes here will not affect the window, new windows or new terminals.

Yep, setting $env:PATH does not change the path at the system level, it only persists for that PowerShell session.  If you want the change to be permanent you need to use System.Environment.SetEnvironmentVariable.  Excerpt from this documentation page:

Like we said, though, that approach only works for process-level environment variables. To create more permanent environment variables (i.e., user-level or machine-level) you need to use the .NET Framework and the SetEnvironmentVariable method.

Hi folks, I appreciate that I wasn't clear in my initial report. I should have made it clear that I was changing the system PATH variable, and by including the temporary fix setting the local terminal PATH variable I muddied the water as to what the issue was, so I'll try to be a bit more specific.
Issue:
VScode is sometimes not picking up system PATH changes even after closing all VScode instances.
I have done some further testing and narrowed things down to the interaction with the quick access menu.
Note for this I uninstalled all extensions.
Recreation:

load a folder in VScode from the quick access menu folder icon (click red below)

change PATH environment variable at the system level (Control panel dialouge etc...)
close ALL VScode instances
open VScode by clicking on the taskbar icon (click white above)
open terminal see the correct PATH variable YAY
close ALL VScode instances
open VScode by clicking on the quick acces menu folder icon (click red above)
open terminal see the out-of-date/incorrect PATH variable

@bpasero apparently the environment is stable when opening via the quick access menu (hover over Taskbar)?

I need the tl;dr; here.
Clicking on the taskbar is the same as running code <folder> from the command line.

Look at recreation section in https://github.com/Microsoft/vscode/issues/20140#issuecomment-278296230

Ok, no idea what's going on, there is defniteley no difference in our code launching from taskbar vs quick menu, so I suspect an upstream issue.

Btw the summary is still talking about something else:

Not detecting env PATH changes made after a VScode instance has been opened

Hi guys thanks for looking at this.
@bpasero Please do go ahead with changing the summary of the bug, I'm not sure if/how to do it myself. At the time I hadn't managed to narrow it down to the quick access menu maybe something along the lines of this would be more appropriate:

Launching VScode from the quick access menu does not correctly inherit system environment variable if a change has been made since first launch.

Sorry corrected it now to the suggetion

Still happening?

I've tested on three computers two of which were running older versions (1.16.1 & 1.17.0) of VS code (one x86), the issue appears to persist. I updated all three computers to the latest version 1.18.0 and tested again as per my comment a #20140 and the issue persists.
Sorry I don't have any new information, if it would be helpful I could spin up a clean windows install in a vm although I have tested across three different computers so far?

I can reproduce but this seems like nothing we can fix on our end because after a restart of Windows the issue disappears.
Closing.

authors: Tyriar bpasero daviwil geoff3jones


text:
Typing an import makes TS unresponsive for > 30s

Type the following, one character at a time (i.e. no copy-paste tricks)
import * as viewEvents from 'vs/editor/common/view/viewEvents';
Observe how errors show up and the entire language service is unresponsive for >30s.
Saw it on Linux, but I don't think it is an OS specific issue
This is highly annoying and blocks me from being productive while selfhosting.
fyi @jrieken

To investigate this, try collecting some logs from the TypeScript server when this occurs. Here's information on to do this using the TSS_LOG environment variable: https://github.com/Microsoft/TypeScript/wiki/Standalone-Server-(tsserver)#logging
From a command prompt, run:
$ export TSS_LOG="-level verbose -file /Users/USERNAME/.tslog"
$ code

Reproduce the problem in VSCode and then share the .tslog file.
Let me know if you have any questions about this.
Thanks

I'd say this is the same as https://github.com/Microsoft/vscode/issues/18792. @mjbvz Are you saying you don't see that?

@mjbvz Here you go:
tslog.txt.tar.gz
Here is also a gif of me typing the import. The gif is not a loop, it eventually comes back ~50s later:

Please let me know if you encounter further difficulties in reproducing.

This is the TS version appearing in the status bar:

And here is the time it takes for tsserver to become responsive when pasting the import:

Notice how fast VS Code 1.8.1 is:

I also saw this slowness today. Intellisense and Diagnostics are very slow. I had to reload to get back to normal state

@mhegazy Can you please take a look here? I don't see anything explicitly going wrong on the VSCode side, but the request queue lengths do quickly build up which I believe causes this behavior.
The reason the queues get so long may be, getCodeFixes which starts out taking only a few ms but ends up taking 3.5 seconds plus in requests later on. I don't see any obvious causes in the TSS_LOGS for this

Thanks everyone. @vladima took in a fix on the TS side  https://github.com/Microsoft/TypeScript/pull/14215 and I also checked in a workaround on our side 02006fe

@mjbvz @vladima Thanks a lot for the fix, I really appreciate it 💯 🚀

authors: alexandrudima jrieken mjbvz sandy081


text:
Select all occurences weird behavior

VSCode Version: 1.9.1
OS Version: Windows 7

The issues title could be rename properly
Ok this on is a bit weird but it's a weird stuff I was doing
In fact, I was regrouping with the multiple line cursor
For the purpose I will give you a "File" (multiple line in the description)
The weird stuff happen with the lines with this KeyWord "WeirdStuffHappenOnThoseLine"
So I give you the example that work well at first and after I will write the instruction that doesn't work as expected
Steps to Reproduce:

Double click on "WhatEverStuff" to select the keyword
Ctrl + F (Open the find tools bar)
Alt + Enter (Select all "WhatEverStuff")
After select all,

Press Alt + Arrow Up Multiple time until every "WhatEverStuff" is at the beginning of the files

For now every "WhatEverStuff" is regroup and no problem have happen right now !!!

Double click on "WeirdStuffHappenOnThoseLine" to select the keyword
Ctrl + F (Open the find tools bar)
Alt + Enter (Select all "WeirdStuffHappenOnThoseLine")
After select all,

Press Alt + Arrow Up until everything is at the beginning of the folder

But you will see that only the first "WeirdStuffHappenOnThoseLine" of each 3 following Keyword has goes down
So you need to Restart step 7 and step 8 two times again to make it regroup and it's no more the same as I would expect to work (every 3 following keyword should goes down at the same time)
File Here :
WhatEverStuff
WorkingStuff
WeirdStuffHappenOnThoseLine 1
WeirdStuffHappenOnThoseLine 2
WeirdStuffHappenOnThoseLine 3
OtherStuffUnneccessary
WhatEverStuff
WorkingStuff
WeirdStuffHappenOnThoseLine 4
WeirdStuffHappenOnThoseLine 5
WeirdStuffHappenOnThoseLine 6
OtherStuffUnneccessary
WhatEverStuff
WorkingStuff
WeirdStuffHappenOnThoseLine 7
WeirdStuffHappenOnThoseLine 8
WeirdStuffHappenOnThoseLine 9
OtherStuffUnneccessary
WhatEverStuff
WorkingStuff
WeirdStuffHappenOnThoseLine 10
WeirdStuffHappenOnThoseLine 11
WeirdStuffHappenOnThoseLine 12
OtherStuffUnneccessary
WhatEverStuff
WorkingStuff
WeirdStuffHappenOnThoseLine 13
WeirdStuffHappenOnThoseLine 14
WeirdStuffHappenOnThoseLine 15
OtherStuffUnneccessary
WhatEverStuff
WorkingStuff
WeirdStuffHappenOnThoseLine 16
WeirdStuffHappenOnThoseLine 17
WeirdStuffHappenOnThoseLine 18
OtherStuffUnneccessary
WhatEverStuff
WorkingStuff
WeirdStuffHappenOnThoseLine 19
WeirdStuffHappenOnThoseLine 20
WeirdStuffHappenOnThoseLine 21
OtherStuffUnneccessary
WhatEverStuff
WorkingStuff
WeirdStuffHappenOnThoseLine 22
WeirdStuffHappenOnThoseLine 23
WeirdStuffHappenOnThoseLine 24
OtherStuffUnneccessary
WhatEverStuff
WorkingStuff

File result after doing step 1 to step 8 one time :
WeirdStuffHappenOnThoseLine 22
WeirdStuffHappenOnThoseLine 19
WeirdStuffHappenOnThoseLine 16
WeirdStuffHappenOnThoseLine 13
WeirdStuffHappenOnThoseLine 10
WeirdStuffHappenOnThoseLine 7
WeirdStuffHappenOnThoseLine 4
WeirdStuffHappenOnThoseLine 1
WhatEverStuff
WhatEverStuff
WhatEverStuff
WhatEverStuff
WhatEverStuff
WhatEverStuff
WhatEverStuff
WhatEverStuff
WhatEverStuff
WorkingStuff
WeirdStuffHappenOnThoseLine 2
WeirdStuffHappenOnThoseLine 3
OtherStuffUnneccessary
WorkingStuff
WeirdStuffHappenOnThoseLine 5
WeirdStuffHappenOnThoseLine 6
OtherStuffUnneccessary
WorkingStuff
WeirdStuffHappenOnThoseLine 8
WeirdStuffHappenOnThoseLine 9
OtherStuffUnneccessary
WorkingStuff
WeirdStuffHappenOnThoseLine 11
WeirdStuffHappenOnThoseLine 12
OtherStuffUnneccessary
WorkingStuff
WeirdStuffHappenOnThoseLine 14
WeirdStuffHappenOnThoseLine 15
OtherStuffUnneccessary
WorkingStuff
WeirdStuffHappenOnThoseLine 17
WeirdStuffHappenOnThoseLine 18
OtherStuffUnneccessary
WorkingStuff
WeirdStuffHappenOnThoseLine 20
WeirdStuffHappenOnThoseLine 21
OtherStuffUnneccessary
WorkingStuff
WeirdStuffHappenOnThoseLine 23
WeirdStuffHappenOnThoseLine 24
OtherStuffUnneccessary
WorkingStuff

By the way I don't know if it suppose to be like this order :

22 19 16 13 10 7 4 1

But I was expecting the sort version like that  :

1 4 7 10 13 16 19 22

I see this too - in short, if you have cursors on multiple consecutive lines, then use "move line up/down", the cursors combine into one and only one line moves

Thanks @roblourens  for the quick and better description :+1:

More steps from @GrantSolar

VSCode Version: 1.10.2
OS Version: Windows 10 x64

When selecting text using columns (either CTRL+SHIFT+ALT+ARROW or SHIFT+ALT+MOUSE1), moving the selected text using ALT+UP/DOWN will always shift the line of the initial cursor position. Shifting the other selected lines appears to depend on whether the selected column exists on the line above.
Steps to Reproduce:

Open a new file and paste in the following contents (note that there is no trailing whitespace):

var a = 'apple crumble';
var b = 'bun';
var c = 'chocolate cake';
var d = 'doughnuts';
var e = 'egg';

Box select from the a in apple crumble to one of the os in chocolate cake
Release all keys then press ALT+DOWN.

Expected result: All 3 selected lines move. Columns are still selected
Line order: d, a, b, c, e
Actual result: Only first line moves. Only first line has column selected
Line order: b, a, c, d, e

Return the file to the original order
Box select from the r in apple crumble to the s in doughnuts
Release all keys then press ALT+DOWN

Expected result: All 3 lines with selected text move. Columns are still selected
Line order: b, a, e, c, d
Actual result: Only first and third lines are moved. Only columns from these 2 lines are selected
Line order: b, a, d, c, e

Hummm I was doing the same type of job today and saw the issue wasn't fixed, was this going to be on the list soon ? I really like to work with regex and multiline edit and this kinda bummer to me and I feel the combine cursor shouldn't work like that. Any plan of doing that they don't combine ? Like if I selecting 3 line with the mouse with no multicursor, the 3 line should follow each other and I would expect the same with the multicursor 3 line in a row selected but it isn't. Ex: I'm selecting the first 3 line of a file with multicursor, the forth line should jump to the first line when doing ALT+DOWN.

RECAP: Mutlicursor "move line up/down" shouldn't combine cursor. Probably fixing that would fix all the issues I have with this feature.
Case scenario: End of file move line down and start of the file move line up

Expect some line not moving when there is already selected line below that can't move

authors: alexandrudima maxime4000 roblourens


text:
Foreground syntax theme wrong   ...

VSCode Version: 1.11.1
OS Version: Mac OS X 10.12.4

Steps to Reproduce:

Update visual studio
My foreground configuration color 	foreground#FFEB3B is now  rgba(187, 187, 187, 1) and I can't change it ? why ?

Which theme are you using?

Polymer Syntax

Author of Polymer Syntax here.
It seems the tokenizer in 1.11.x regressed or broke and now just about every theme and highlighter is deformed.

@bpasero can you please verify?

@aeschli any steps?

@bpasero

install Polymer Syntax Theme
open a .md file
use the Inspect TM scopes command on the default foreground color
verify that the color is #F8F8F8 as specified in the theme specification

Thanks, verified.

authors: JonathanWolfe aeschli bpasero chrmarti imacnu isidorn


text:
vscode中启动调试js时，总是自动打开输入窗口，还得手动点下旁边的调试控制台才可以看到输出，如何自动打开输出控制台？

VSCode Version:1.10.2
OS Version:ubuntu 16.04

Steps to Reproduce:
1.f5调试一个js文件或者ts文件
2.在调试控制台查看打印的内容

https://stackoverflow.com/questions/42796887/switch-focus-between-editor-and-integrated-terminal-in-visual-studio-code/43012779
Maybe you can use keyboard shortcuts instead of clicking around.

@chaojihexiang Please file this issue in English

Closing because this issue is without actionable information.

authors: chaojihexiang guhuajun jrieken


text:
Zen Mode Freezed , now can't able to kill the process also

I was just trying out the zen mode for the first time in vscode
I am using ubuntu 16.x .
All of a suddent zen mode freezes and I can't able to kill the process, every time I use
kill -9 <pid>
as root still no luck , the process is running
root@jeyanthinath-ThinkPad:~# ps -eaf | grep 1831
jeyanth+ 18318  6277  0 17:28 ?        00:00:00 [code] <defunct>
root     25206 25184  0 19:14 pts/18   00:00:00 grep --color=auto 1831
root@jeyanthinath-ThinkPad:~#
root@jeyanthinath-ThinkPad:~# kill -9 18318
root@jeyanthinath-ThinkPad:~#
root@jeyanthinath-ThinkPad:~# kill -9 18318
root@jeyanthinath-ThinkPad:~# ps -eaf | grep 1831
jeyanth+ 18318  6277  0 17:28 ?        00:00:00 [code] <defunct>
root     25227 25184  0 19:14 pts/18   00:00:00 grep --color=auto 1831

The Screenshot

with refering to this answer , I can assume that kill -9 works for sure , but what is going wrong around here?

@Jeyanthinath when you say that vscode freezes that means that you can not type and it is not responsive in any way?
Can you also reproduce this when you simply go to full screen View > toggle full screen?
If answer to previous question is yes, can you also reproduce with a simple eletron quick start example https://github.com/electron/electron-quick-start
Can you also reproduce if you use latest vscode insiders https://code.visualstudio.com/insiders
Thanks

@isidorn vscode freezes and I can't able to use it anyway, I tried opening the new instances and still I can't connect to them also , can't kill them also
version : 1.12.1
I haven't used zen mode from that time, may be I will try for a while and will update on this

Ok. Please try answering my questions from above when you have a chance.

authors: Jeyanthinath isidorn


text:
Wrong TextEditorSelectionChangeKind for click inside a selection

VSCode Version: Code 1.13.1
OS Version: Darwin x64 15.6.0
no extensions

The TextEditorSelectionChangeKind.Command is fired instead of TextEditorSelectionChangeKind.Mouse when a click occur inside a selection.
Steps to Reproduce:

Select few lines
click anywhere inside the selection

The code running in the exemple :
'use strict';
import {
  window,
  ExtensionContext,
  TextEditorSelectionChangeEvent,
  TextEditorSelectionChangeKind
} from 'vscode';

export function activate(context: ExtensionContext) {
    window.onDidChangeTextEditorSelection((event: TextEditorSelectionChangeEvent) => {
		// 1: Keyboard
		// 2: Mouse
		// 3: Command
		console.log(`Event kind : ${event.kind}`)
	}, null, context.subscriptions);
}
export function deactivate() {}

The convert-logic checks for command and mouse...

The kind is informative as best, flaky, and perhaps should never have been exposed as API, but I think we had an extension in terrible need of it.
The root cause here is: in this specific case, it is a recently added editor contribution (the dnd code), and not the editor core that reacts to the mouse move event and uses internal editor api to set the selection, that's why now the event reason is 'api'. Disabling dnd will probably make the kind in this case be mouse again...

I can confirm that setting "editor.dragAndDrop": false successfully works around this bug.

authors: KamiKillertO alexandrudima jpotterm jrieken


text:
[Folding] Actions on folded section only effects first line

VSCode Version: 1.16.0
OS Version: Centos 7

Steps to Reproduce:

Fold a section of code
Select folded section
Press delete, or alt+(up or down), or copy and paste

Reproduces without extensions: Yes

How did you select the folded region?
You have to select up to the next line if you want to work on the whole folded range.
Otherwise, it's really just the one line

authors: aeschli bofabcd


text:
Global Search is only returning results from opened files

Issue Type
Bug
Description

open new folder
search for a keyword
no result
open a file(including the keyword above) from the folder
search for the keyword again
result only from opened files

VS Code Info
VS Code version: Code 1.20.0 (c63189deaa8e620f650cc28792b8f5f3363f2c5b, 2018-02-07T17:10:31.920Z)
OS version: Windows_NT ia32 6.1.7601

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz (8 x 2594)

Memory (System)
7.92GB (2.21GB free)

Process Argv
C:\Program Files (x86)\Microsoft VS Code\Code.exe

Screen Reader
no

VM
0%

Extensions (13)

Extension
Author (truncated)
Version

vscode-eslint
dba
1.4.5

gitlens
eam
8.0.0

team
ms-
1.122.0

vscode-boot-dev-pack
Piv
0.0.2

vscode-boot-java
Piv
0.1.3

vscode-boot-properties
Piv
0.1.3

vscode-concourse
Piv
0.1.3

vscode-manifest-yaml
Piv
0.1.3

java
red
0.18.1

angular-follow-selector
san
1.1.1

vscode-angular-support
vis
0.1.4

vscode-java-debug
vsc
0.6.0

vscode-java-pack
vsc
0.2.0

Reproduces without extensions

@bluefunc90 I'm not sure how this was off my radar for so long. I think the issue has some missing history. Is this still a problem on the latest version?

@roblourens Thanks for the response and you don't have to worry about the delay. The delay was because there were some problems on my github account.. And you don't have to worry about this issue too, because the problem's gone on the latest version. Thank you very much.


text:
Extreme CPU usage when multiple windows are open

Version

VSCode Version: 1.21.1
OS Version: macOS High Sierra 10.13.3 (17D102)

Steps to Reproduce:

Open two separate VS Code windows (different projects).
After a while (randomly) CPU usage will spike.
Close one of the windows, and the issue is resolved.

CPU Profile:
Issue seems to stop as soon as I try to perform a CPU Profile via the developer tools in VS Code. I have attempted to produce a profile though, right when the issue started.
CPU-20180328T192331.cpuprofile.zip
Status output:
2018-03-25:
Version:          Code 1.21.1 (79b44aa704ce542d8ca4a3cc44cfca566e7720f1, 2018-03-14T14:39:09.335Z)
OS Version:       Darwin x64 17.4.0
CPUs:             Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz (8 x 2900)
Memory (System):  16.00GB (1.23GB free)
Load (avg):       3, 3, 3
VM:               0%
Screen Reader:    no
Process Argv:     /Applications/Visual Studio Code.app/Contents/MacOS/Electron -psn_0_278596

CPU %	Mem MB	   PID	Process
   80	   115	   720	code main
    0	    82	   749	   gpu-process
    1	    66	   777	   shared-process
   77	   311	 58876	   window (FILE.js — PROJECT)
    0	    82	 58877	     extensionHost
    0	   164	 58896	       electron_node electronForkStart.js tsserver.js
    0	    33	 58898	         electron_node typingsInstaller.js tsserver.js typesMap.js
    0	    16	 59227	       electron_node jsonServerMain.js
    0	    16	 60181	       electron_node cssServerMain.js
    0	    33	 58878	     watcherService
    0	    33	 58881	     searchService
    0	   246	 71535	   window (FILE.js — PROJECT)
    0	    98	 71536	     extensionHost
    0	   147	 71539	       electron_node electronForkStart.js tsserver.js
    0	    49	 71553	         electron_node typingsInstaller.js tsserver.js typesMap.js
    0	    49	 74572	       electron_node jsonServerMain.js
    0	    33	 71541	     searchService
    0	    33	 72049	     watcherService

Workspace Stats:
|  Window (FILE.js — PROJECT)
|    Folder (PROJECT): 128 files
|      File types: js(37) jade(19) json(13) png(11) md(3) svg(3) css(3) txt(2)
|                  ico(2) styl(2)
|      Conf files: package.json(1)
|  Window (FILE.js — PROJECT)
|    Folder (PROJECT): more than 20000 files
|      File types: txt(18470) json(83) wt(57) js(57) tsm(15) wal(14)
|                  DS_Store(9) map(5) conf(4) db(2)
|      Conf files:

2018-03-28:
Version:          Code 1.21.1 (79b44aa704ce542d8ca4a3cc44cfca566e7720f1, 2018-03-14T14:39:09.335Z)
OS Version:       Darwin x64 17.4.0
CPUs:             Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz (8 x 2900)
Memory (System):  16.00GB (0.37GB free)
Load (avg):       4, 3, 3
VM:               0%
Screen Reader:    no
Process Argv:     /Applications/Visual Studio Code.app/Contents/MacOS/Electron

CPU %	Mem MB	   PID	Process
   63	    98	 76657	code main
    0	    49	 76658	   gpu-process
   77	   573	 76659	   window (app.js — PROJECT)
    0	   147	 76666	     extensionHost
    0	   115	 76672	       electron_node electronForkStart.js tsserver.js
    0	    33	 76684	         electron_node typingsInstaller.js tsserver.js typesMap.js
    0	    98	 83222	       electron_node jsonServerMain.js
    0	    16	 76670	     searchService
    0	   115	 76660	   shared-process

Workspace Stats:
|  Window (FILE.js — PROJECT)
|    Folder (PROJECT): more than 20000 files
|      File types: txt(18447) json(83) js(58) wt(57) wal(26) tsm(26)
|                  DS_Store(9) map(5) conf(4) db(2)
|      Conf files:
|  Window (FILE.js — PROJECT)
|    Folder (PROJECT): 128 files
|      File types: js(37) jade(19) json(13) png(11) md(3) svg(3) css(3) txt(2)
|                  ico(2) styl(2)
|      Conf files: package.json(1)

2018-03-30:
Version:          Code 1.21.1 (79b44aa704ce542d8ca4a3cc44cfca566e7720f1, 2018-03-14T14:39:09.335Z)
OS Version:       Darwin x64 17.4.0
CPUs:             Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz (8 x 2900)
Memory (System):  16.00GB (0.29GB free)
Load (avg):       3, 3, 3
VM:               0%
Screen Reader:    no
Process Argv:     /Applications/Visual Studio Code.app/Contents/MacOS/Electron

CPU %	Mem MB	   PID	Process
   77	    82	 46056	code main
    0	    66	 46057	   gpu-process
    0	   311	 46058	   window (FILE.js — PROJECT)
    0	   115	 46065	     extensionHost
    0	   131	 46072	       electron_node electronForkStart.js tsserver.js
    0	    33	 46084	         electron_node typingsInstaller.js tsserver.js typesMap.js
    0	    33	 71259	       electron_node jsonServerMain.js
    0	    16	 46066	     watcherService
    0	    16	 46070	     searchService
    0	    82	 46059	   shared-process
   80	   262	 76600	   window (FILE.js — PROJECT)
    0	    66	 76601	     extensionHost
    0	   180	 76648	       electron_node electronForkStart.js tsserver.js
    0	    16	 76660	         electron_node typingsInstaller.js tsserver.js typesMap.js
    0	    33	 95052	       electron_node jsonServerMain.js
    0	    16	 76602	     watcherService
    0	    16	 76646	     searchService

Workspace Stats:
|  Window (FILE.js — PROJECT)
|    Folder (PROJECT): more than 20000 files
|      File types: txt(18447) json(83) js(58) wt(57) wal(26) tsm(26)
|                  DS_Store(9) map(5) conf(4) db(2)
|      Conf files:
|  Window (FILE.js — PROJECT)
|    Folder (PROJECT): 130 files
|      File types: js(38) jade(19) json(13) png(11) md(3) svg(3) css(3) txt(2)
|                  ico(2) styl(2)
|      Conf files: package.json(1)

Duplicate of #41557. I also use witch for task switching.
Related to #38516.


text:
golang debug

VSCode Version:1.22.1
OS Version:OSX 10.13.3 (17D102)

Steps to Reproduce:
1.All of go extensions are installed.
2.F5 to start debugging, then
2018/04/10 17:26:07 server.go:73: Using API v1
2018/04/10 17:26:07 debugger.go:98: launching process with args: [/Users/xiexiaomei/go/src/test/debug]
could not launch process: EOF
Process exiting with code: 1

Please file this issue against the go debugger.

authors: XieXiaomei-ptr weinand