Deployment socket hung in Visual Studio - manual deployement
See original GitHub issueHi Team, We are facing the same issue again with the below-mentioned version
Version: 1.66.0 (user setup) Commit: e18005f0f1b33c29e81d732535d8c0e47cafb0b5 Date: 2022-03-30T05:50:14.623Z Electron: 17.2.0 Chromium: 98.0.4758.109 Node.js: 16.13.0 V8: 9.8.177.11-electron.0 OS: Windows_NT x64 10.0.18363
Past issue reference:
#2108
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Deploying to Azure Functions with message "socket hang up ...
Created an Azure Function in Visual Studio Code and deployed it succesfully at first. When adding a second function, it failed after ...
Read more >Not able to deploy app on Azure App Services using VS Code
I have created an API in python and I'm trying deploy my app on Azure App ... isAsync=true&author=VS%20Code failed, reason: socket hang up...
Read more >Visual Studio get stuck always during app deployment on azure
And after several minutes of waiting: azure deployment failed, reason: socket hang up. Note: app is just simple nodejs express sample app ...
Read more >UniversalPackages task fails with socket hang up error behind ...
This error shows up consistently in pipeline runs. Successful run logs: 2020-03-26T03:19:57.0660140Z ##[debug]Getting artifact tool 2020-03-26T03:19: ...
Read more >Troubleshoot Cloud Run issues
Deployment errors. This section lists issues that you might encounter with deployment and provides suggestions for how to fix each of them. Container...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Until a fix is released in VS Code stable (hopefully the next major release), here are some options:
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 in1.3.0(Mar 15, 2021).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.
Fix working thanks, @alexweininger