You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Below is the stack trace. Unfortunately, it was broken for so long without me noticing I was not able to find what actually triggered it. I did not see this with any other server.js errors in issues.
c:\Users\user\.vscode\extensions\ms-azure-devops.azure-pipelines-1.208.0\dist\server.js:1903
item.mappings[0].key.value.startsWith("${{") &&
^
TypeError: Cannot read properties of undefined (reading 'key')
at addItemsToArrayNode (c:\Users\user\.vscode\extensions\ms-azure-devops.azure-pipelines-1.208.0\dist\server.js:1903:34)
at recursivelyBuildAst (c:\Users\user\.vscode\extensions\ms-azure-devops.azure-pipelines-1.208.0\dist\server.js:1814:13)
at recursivelyBuildAst (c:\Users\user\.vscode\extensions\ms-azure-devops.azure-pipelines-1.208.0\dist\server.js:1806:48)
at addPropertiesToObjectNode (c:\Users\user\.vscode\extensions\ms-azure-devops.azure-pipelines-1.208.0\dist\server.js:1883:30)
at recursivelyBuildAst (c:\Users\user\.vscode\extensions\ms-azure-devops.azure-pipelines-1.208.0\dist\server.js:1794:13)
at recursivelyBuildAst (c:\Users\user\.vscode\extensions\ms-azure-devops.azure-pipelines-1.208.0\dist\server.js:1806:48)
at addPropertiesToObjectNode (c:\Users\user\.vscode\extensions\ms-azure-devops.azure-pipelines-1.208.0\dist\server.js:1883:30)
at recursivelyBuildAst (c:\Users\user\.vscode\extensions\ms-azure-devops.azure-pipelines-1.208.0\dist\server.js:1794:13)
at recursivelyBuildAst (c:\Users\user\.vscode\extensions\ms-azure-devops.azure-pipelines-1.208.0\dist\server.js:1806:48)
at addPropertiesToObjectNode (c:\Users\user\.vscode\extensions\ms-azure-devops.azure-pipelines-1.208.0\dist\server.js:1883:30)
[Error - 4:56:47 PM] Connection to server got closed. Server will not be restarted.
The text was updated successfully, but these errors were encountered:
Below is the stack trace. Unfortunately, it was broken for so long without me noticing I was not able to find what actually triggered it. I did not see this with any other server.js errors in issues.
The text was updated successfully, but these errors were encountered: