microsoft/azure-pipelines-vscode

TypeError: Expected signal to be an instanceof AbortSignal

pkrukp opened this issue · 2 comments

pkrukp commented

Hi,

I'm getting "TypeError: Expected signal to be an instanceof AbortSignal" when running "Azure Pipeline: Configure Pipeline". I select "Simple Application to Windows Web App", then select my Subscription, then the error happens.

Console shows:

mainThreadExtensionService.ts:64 TypeError: Expected signal to be an instanceof AbortSignal
	at new H (c:\Users\pkruk\.vscode\extensions\ms-vscode.azure-account-0.9.8\dist\extension.js:253:17134)
	at c:\Users\pkruk\.vscode\extensions\ms-vscode.azure-account-0.9.8\dist\extension.js:253:18457
	at new Promise (<anonymous>)
	at G (c:\Users\pkruk\.vscode\extensions\ms-vscode.azure-account-0.9.8\dist\extension.js:253:18420)
	at t.<anonymous> (c:\Users\pkruk\.vscode\extensions\ms-azure-devops.azure-pipelines-1.188.1\dist\extension.js:2:726791)
	at c:\Users\pkruk\.vscode\extensions\ms-azure-devops.azure-pipelines-1.188.1\dist\extension.js:2:1649941
	at Object.next (c:\Users\pkruk\.vscode\extensions\ms-azure-devops.azure-pipelines-1.188.1\dist\extension.js:2:1650046)
	at c:\Users\pkruk\.vscode\extensions\ms-azure-devops.azure-pipelines-1.188.1\dist\extension.js:2:1648983
	at new Promise (<anonymous>)
	at n (c:\Users\pkruk\.vscode\extensions\ms-azure-devops.azure-pipelines-1.188.1\dist\extension.js:2:1648728)
	at t.fetch (c:\Users\pkruk\.vscode\extensions\ms-azure-devops.azure-pipelines-1.188.1\dist\extension.js:2:726717)
	at t.<anonymous> (c:\Users\pkruk\.vscode\extensions\ms-azure-devops.azure-pipelines-1.188.1\dist\extension.js:2:725345)
	at c:\Users\pkruk\.vscode\extensions\ms-azure-devops.azure-pipelines-1.188.1\dist\extension.js:2:1649941
	at Object.next (c:\Users\pkruk\.vscode\extensions\ms-azure-devops.azure-pipelines-1.188.1\dist\extension.js:2:1650046)
	at n (c:\Users\pkruk\.vscode\extensions\ms-azure-devops.azure-pipelines-1.188.1\dist\extension.js:2:1648785)
	at processTicksAndRejections (internal/process/task_queues.js:93:5)

From what I google it might be problem with webpack minimalization in production build...

Versions:
Azure Pipelines 1.188.1
VSCode:
Version: 1.58.2 (user setup)
Commit: c3f126316369cd610563c75b1b1725e0679adfb3
Date: 2021-07-14T22:10:15.214Z
Electron: 12.0.13
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: 8.9.255.25-electron.0
OS: Windows_NT x64 10.0.19043

molotch commented

I have the exact same problem.

VSCode:

Version: 1.60.0 (user setup)
Commit: e7d7e9a9348e6a8cc8c03f877d39cb72e5dfb1ff
Date: 2021-09-01T10:41:52.311Z
Electron: 13.1.8
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19042

Azure Pipelines extension:
v1.191.0

I run VScode throught the server in WSL2 if that makes a difference.

50Wliu commented

Version 1.195.0 of the extension has been released. Let me know if you still have issues after updating.