vscode
vscode copied to clipboard
microsoft
deploy app to azure "The request was aborted"
every time i deply my app to azure i get this string of events: 12:48:11 PM floatracing: Starting deployment... 12:48:13 PM floatracing: Creating zip package... 12:48:14 PM floatracing: Ignoring files from "appService.zipIgnorePattern" "node_modules{,/}" ".vscode{,/}" 12:54:22 PM floatracing: Zip package size: 430 MB 12:54:37 PM: Error: The request was aborted
however, when i go to azure and check my deployment center, the deployment still follows through successfully.
this has probably been ging on for at least a week or so... maybe 2?
and before that it worked as expected and showed each and every status update as the deployment process progressed.
i have not made any settings changes in vscode or azure.
Same here but for me sometimes it fails the deployment at Azure portal as well.
Same issue here, this happens randomly and if I try a couple of times it will pass successfully at some point.
Same issues here. No error given just says request failed. Initial creation of app service worked, but any following deployments fail.
Hello there, Same with me is happening today. After update from Visual Studio Code it started happening the error to me. The problem it is to me that the process brakes and my code will not be deployed.
4:48:03 PM career-backend: Starting deployment...
4:48:05 PM career-backend: Creating zip package...
4:48:37 PM career-backend: Zip package size: 101 MB
4:48:47 PM career-backend: Fetching changes.
4:48:49 PM career-backend: Cleaning up temp folders from previous zip deployments and extracting pushed zip file /tmp/zipdeploy/b5116e3e-5009-473d-a8a5-4288f900461a.zip (97.05 MB) to /tmp/zipdeploy/extracted
4:49:50 PM career-backend: Updating submodules.
4:49:51 PM career-backend: Preparing deployment for commit id 'b6512bb9-0'.
4:49:51 PM career-backend: PreDeployment: context.CleanOutputPath False
4:49:51 PM career-backend: PreDeployment: context.OutputPath /home/site/wwwroot
4:49:52 PM career-backend: Repository path is /tmp/zipdeploy/extracted
4:49:52 PM career-backend: Running oryx build...
4:49:52 PM career-backend: Command: oryx build /tmp/zipdeploy/extracted -o /home/site/wwwroot --platform nodejs --platform-version 14 -i /tmp/8da762896111afd -p compress_node_modules=tar-gz --log-file /tmp/build-debug.log | tee /tmp/oryx-build.log
4:49:56 PM career-backend: Operation performed by Microsoft Oryx, https://github.com/Microsoft/Oryx
4:49:56 PM career-backend: You can report issues at https://github.com/Microsoft/Oryx/issues
4:49:56 PM career-backend: Oryx Version: 0.2.20220308.4, Commit: c92fa6a2d6fc14dc9646f80e2bb2e393a5cdc258, ReleaseTagName: 20220308.4
4:49:57 PM career-backend: Build Operation ID: |5h6hsXPIw+M=.3e033129_
4:49:57 PM career-backend: Repository Commit : b6512bb9-0214-4b22-816f-e3f74c1f90dc
4:49:57 PM career-backend: Detecting platforms...
4:50:03 PM career-backend: Detected following platforms:
4:50:03 PM career-backend: nodejs: 14.19.1
4:50:05 PM career-backend: Using intermediate directory '/tmp/8da762896111afd'.
4:50:06 PM career-backend: Copying files to the intermediate directory...
4:50:06 PM career-backend: Done in 0 sec(s).
4:50:06 PM career-backend: Source directory : /tmp/8da762896111afd
4:50:06 PM career-backend: Destination directory: /home/site/wwwroot
4:50:06 PM career-backend: Removing existing manifest file
4:50:06 PM career-backend: Creating directory for command manifest file if it doesnot exist
4:50:06 PM career-backend: Creating a manifest file...
4:50:06 PM career-backend: Node Build Command Manifest file created.
4:50:06 PM career-backend: Using Node version:
4:50:06 PM career-backend: v14.19.1
4:50:07 PM career-backend: Using Npm version:
4:50:08 PM career-backend: 6.14.16
4:50:08 PM career-backend: Running 'npm install --unsafe-perm'...
4:50:31 PM: Error: The request was aborted
Are people using an extension for this? If so, could it be an issue with the extension to report?
Are people using an extension for this? If so, could it be an issue with the extension to report?
Yes I am using the Azure Extension.
For all of you that having this error. I could not find why is this happening but the deplyoment through Extension in background workd but only the Logs in VS Code are saying the Process is Aborted.
Still searching for a solution if I find I will let u know.
This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines.
Happy Coding!
same issue here, every 1st time deploy would got aborted and the second time will go pretty normally. However, in general the deployment takes much longer than before.
Hello there, Same with me is happening today. After update from Visual Studio Code it started happening the error to me. The problem it is to me that the process brakes and my code will not be deployed.
4:48:03 PM career-backend: Starting deployment... 4:48:05 PM career-backend: Creating zip package... 4:48:37 PM career-backend: Zip package size: 101 MB 4:48:47 PM career-backend: Fetching changes. 4:48:49 PM career-backend: Cleaning up temp folders from previous zip deployments and extracting pushed zip file /tmp/zipdeploy/b5116e3e-5009-473d-a8a5-4288f900461a.zip (97.05 MB) to /tmp/zipdeploy/extracted 4:49:50 PM career-backend: Updating submodules. 4:49:51 PM career-backend: Preparing deployment for commit id 'b6512bb9-0'. 4:49:51 PM career-backend: PreDeployment: context.CleanOutputPath False 4:49:51 PM career-backend: PreDeployment: context.OutputPath /home/site/wwwroot 4:49:52 PM career-backend: Repository path is /tmp/zipdeploy/extracted 4:49:52 PM career-backend: Running oryx build... 4:49:52 PM career-backend: Command: oryx build /tmp/zipdeploy/extracted -o /home/site/wwwroot --platform nodejs --platform-version 14 -i /tmp/8da762896111afd -p compress_node_modules=tar-gz --log-file /tmp/build-debug.log | tee /tmp/oryx-build.log 4:49:56 PM career-backend: Operation performed by Microsoft Oryx, https://github.com/Microsoft/Oryx 4:49:56 PM career-backend: You can report issues at https://github.com/Microsoft/Oryx/issues 4:49:56 PM career-backend: Oryx Version: 0.2.20220308.4, Commit: c92fa6a2d6fc14dc9646f80e2bb2e393a5cdc258, ReleaseTagName: 20220308.4 4:49:57 PM career-backend: Build Operation ID: |5h6hsXPIw+M=.3e033129_ 4:49:57 PM career-backend: Repository Commit : b6512bb9-0214-4b22-816f-e3f74c1f90dc 4:49:57 PM career-backend: Detecting platforms... 4:50:03 PM career-backend: Detected following platforms: 4:50:03 PM career-backend: nodejs: 14.19.1 4:50:05 PM career-backend: Using intermediate directory '/tmp/8da762896111afd'. 4:50:06 PM career-backend: Copying files to the intermediate directory... 4:50:06 PM career-backend: Done in 0 sec(s). 4:50:06 PM career-backend: Source directory : /tmp/8da762896111afd 4:50:06 PM career-backend: Destination directory: /home/site/wwwroot 4:50:06 PM career-backend: Removing existing manifest file 4:50:06 PM career-backend: Creating directory for command manifest file if it doesnot exist 4:50:06 PM career-backend: Creating a manifest file... 4:50:06 PM career-backend: Node Build Command Manifest file created. 4:50:06 PM career-backend: Using Node version: 4:50:06 PM career-backend: v14.19.1 4:50:07 PM career-backend: Using Npm version: 4:50:08 PM career-backend: 6.14.16 4:50:08 PM career-backend: Running 'npm install --unsafe-perm'... 4:50:31 PM: Error: The request was aborted
It's a complete mirror of mine too
