Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deployment socket hung in Visual Studio - manual deployement #3098

Closed
MuhamedSalihSeyedIbrahim opened this issue Apr 6, 2022 · 7 comments
Closed

Comments

@MuhamedSalihSeyedIbrahim

Hi 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

@ghost
Copy link

ghost commented Apr 6, 2022

Not a solution, but I worked around this on my end by downgrading to the February 2022 release:
https://code.visualstudio.com/updates/v1_65

@lainean
Copy link

lainean commented Apr 6, 2022

Same issue. Deployment to Function App from VSCode fails with VSCode version 1.66 but works with previous version 1.65.2.
Deployment 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

@MuhamedSalihSeyedIbrahim
Copy link
Author

MuhamedSalihSeyedIbrahim commented Apr 6, 2022

@luffespresso - thanks for the walk around

@lainean - thanks for confirming the issue

To bring Notice to the team i have opened this issue.

Hope the issue is fixed soon with future update or a patch up

Thanks

@alexweininger
Copy link
Member

alexweininger commented Apr 6, 2022

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
Copy link
Member

Closing as a duplicate of #2844

@alexweininger
Copy link
Member

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

@MuhamedSalihSeyedIbrahim
Copy link
Author

Fix working thanks, @alexweininger

@microsoft microsoft locked and limited conversation to collaborators May 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants