Socket hang up when deploying Azure Functions

[christiangartner]

Deployment using Azure Functions Extension (Deploy to Function App...) fails with VSCode version 1.66. When changed to previous version 1.65.2 of VSCode, everything works fine.

Azure Functions output logs:
9:45:47 AM xx-functions: Starting deployment...
9:45:51 AM xx-functions: Creating zip package...
9:46:06 AM xx-functions: Zip package size: 20.2 MB
10:01:42 AM: Error: request to https://xx-functions.scm.azurewebsites.net/api/zipdeploy?isAsync=true&author=VS%20Code failed, reason: socket hang up

This is a copy of a closed issue created from lainean in vscode-project: microsoft/vscode#146885

[YipingRuan]

Same here and as discussed rollback vscode fixed the issue.

More at https://docs.microsoft.com/en-us/answers/questions/795409/azure-function-vscode-stuck-on-deploying-to-34xxxx.html

Another copy of closed issue ; #2390

[WillyMoselhy]

Same here
BROKEN: VS Code 1.66.0 - Azure Function Extension 1.6.1
WORKING: VS Code 1.65.2 - Azure Function Extension 1.6.1

[alexweininger]

Until a fix is released in VS Code stable (hopefully the next major release), here are some options:

1. Wait for the fix to come in VS Code Insiders
2. Deploy via Azure CLI
3. Downgrade your Azure Functions extension version to 1.2.1 (Feb 08, 2021), we used a different zip deploy method which seems to be working still. Note: it might not work in environments like WSL or Codespaces, which is why we changed our deploy in 1.3.0 (Mar 15, 2021).
4. Downgrade to the VS Code February 2022 release, where zip deploy is working as discussed and confirmed above.

---

Here's some information on the bug we suspect is causing the issue with zip deploy.

We suspect that it was a regression in the libuv library caused by libuv/libuv@ce15b84, which was included in Node.JS 16.13.0.

See this issue, and specifically this comment for more information.

---

Follow along with #2844 for more updates and discussion, we're directing all of these zip deploy issues over there.

[alexweininger]

Closing as a duplicate of #2844

[alexweininger]

Fix has been released in version v1.6.2 of the extension.