fix: vs code launch config: add --disable-concurrency flag for wskdeb…

…ug (#128)

With multiple clusters Openwhisk can create multiple containers for a concurrent action even with minimal traffic. Invocations in a cluster will create a new container in the same cluster. If invocations (actual invocation to debug vs. wskdebug polling) happen in different clusters, there will be 2 containers and they won't see each other, and wskdebug will fail to catch any invocations. Uses the activation db polling agent.

generators/add-vscode-config/VsCodeConfiguration.js

@@ -93,7 +93,8 @@ function createPwaNodeLaunchConfiguration (params) {
     runtimeArgs: [
       `${packageName}/${actionName}`,
       `\${workspaceFolder}/${actionFileRelativePath}`,
-      '-v'
+      '-v',
+      '--disable-concurrency'
     ]
   }
 }

test/generators/add-vscode-config/VsCodeConfiguration.test.js

@@ -93,7 +93,8 @@ test('createPwaNodeLaunchConfiguration', () => {
     runtimeArgs: [
       `${params.packageName}/${params.actionName}`,
       `\${workspaceFolder}/${params.actionFileRelativePath}`, // eslint-disable-line no-template-curly-in-string
-      '-v'
+      '-v',
+      '--disable-concurrency'
     ]
   })
 })

test/generators/add-vscode-config/index.test.js

@@ -71,6 +71,7 @@ const createTestLaunchConfiguration = (packageName) => {
           `${packageName}/__secured_action-1`,
           '${workspaceFolder}/src/actions/action-1', // eslint-disable-line no-template-curly-in-string
           '-v',
+          '--disable-concurrency',
           '--kind',
           'nodejs:14'
         ]