vscode: Deployment to Azure Function Fails with reason: read ECONNRESET
Does this issue occur when all extensions are disabled?: Yes/No
- VS Code Version: 1.66.0
- OS Version: Windows 10
Steps to Reproduce:
- Attempt to deploy to an Azure Function using Azure Function extension fails with the error “reason: read ECONNRESET”
- I downgraded VSCode to version 1.65.2 and the deployment started working again
- I have disabled automatic updates for the time being.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 12
- Comments: 34 (18 by maintainers)
Just to update on the progress, the azure extension team is working on a minimal repro with Nodejs to see if there is already a fix in newer versions that can be backported and at the same time identify the commit which caused this behavior change.
It is still failing with version 1.66.2.
Important for testing - if the zip file is ~10 kB or less, it works. Make sure your test cases are larger than 10 kB or you’ll get false successes.
Fails when > 10kB
Success when < 10kB
Version
Sorry for the confusion, the electron build numbers don’t change, backports have been made to the same version. What would change in these cases is
process.versions["microsoft-build"]
Since it is confirmed that insiders does not fix the issue, I would need to investigate further with E2E setup. I will update here once there is some progress.
Very likely regressed with https://github.com/libuv/libuv/commit/ce15b8405e9d01e221f8390475deab4a40d26e38, need to test with Nodejs
>= 16.14.0
that contains https://github.com/libuv/libuv/commit/b2614a10a579ae6e9936eb483fe5ce14aa65a212 and https://github.com/nodejs/node/commit/3b5b893abb1d2929673386204d870e5f138ec3d0. Refs https://github.com/nodejs/node/issues/39683I am also experiencing this issue deploying a function app.
Reverting to version 1.65.2 (user setup) fixed the issue.
Fix has been released in version v1.6.2 of the Azure Functions extension. 🎉
@alexweininger yup I am working on the build, will update here once it is available for testing. Thanks for the help!
I am on 1.66.0 and also experience this problem. Installing https://code.visualstudio.com/updates/v1_65 instead solved the problem.
I can confirm that deployment is now working with VS Code v1.66 and Azure Functions Extension v1.6.2. Thank you everyone for your help.
@isidorn yup the issue has been isolated to a third-party module used by the extension whose behavior regressed with some changes to the Nodejs streams component. I have been syncing with @alexweininger offline, we can close this issue as it does not require any work from core and can be addressed on the extension side.
@LidorPrototype please file a new issue on the Azure Functions extension, thanks!
@deepak1556
I just tried insiders build but that doesn’t seems to address the issue. Same issue of
ECONNRESET
.FYI, A new version of Azure Function Core Tools was released, version 4.0.4426. I did this update and then reinstalled VS Code 1.66.0. This did NOT fix the issue. I still get the same error when trying to deploy to Azure
@jrieken @chrmarti I outlined this in #146577, but will repeat here in case it provides more context to the issue:
I found that setting
NODE_DEBUG=stream
while debugging the Azure Functions extension somehow fixes the issue. WithoutNODE_DEBUG=stream
, I can reproduce the issue consistently. Any insight?