Exception in extracting and setting permissions on the zip file

[the1abel]

Bug Report

Situation:

I'm using VS Code's Azure App Service extension to deploy a web app from a Windows DaaS; but it fails a high percentage of the time, commonly with the Error Message pasted below.
The web app's Runtime Stack is "Node - 20-lts", which uses a container image running Debian GNU/Linux 12 (bookworm).
My Publishing model is "Code".

Error Message:

Exception in extracting and setting permissions on the zip file System.IO.Abstractions.FileInfoWrapper:System.IO.InvalidDataException: Offset to Central Directory cannot be held in an Int64.
    at System.IO.Compression.ZipArchive.ReadEndOfCentralDirectory()
    at System.IO.Compression.ZipArchive..ctor(Stream , ZipArchiveMode , Boolean , Encoding )
    at System.IO.Compression.ZipArchive..ctor(Stream , ZipArchiveMode )
    at Kudu.Services.Deployment.PushDeploymentController.LocalZipFetch(IRepository repository, DeploymentInfoBase deploymentInfo, String targetBranch, ILogger logger, ITracer tracer) in /tmp/KuduLite/Kudu.Services/Deployment/PushDeploymentController.cs:line 934

This error can be seen in the VS Code Output (lower panel) for Azure App Service, but the file path (in the 3rd line below 3) indicates that the error is occurring in the container running in Azure, not on the DaaS, indicated by the POSIX (Linux) file path (uses forward slashes instead of Windows back slashes, and this path does not exist on my DaaS).

These are the 3 output lines that precede the above Error Message:

Zip package size: 119 MB
Fetching changes.
Cleaning up temp folders from previous zip deployments and extracting pushed zip file /tmp/zipdeploy/2a055ec1-9af2-43a1-ad8b-c1e8d6b90b53.zip (85.74 MB) to /tmp/zipdeploy/extracted

• At what date and time did you most recently experience the problem?
  Today, but it has occurred for at least a few days.

• Where did you experience the problem? E.g. Azure Web Apps, Azure Functions, Azure Container Registry, or offline use.
  Azure Web App, error occurring in the container following deployments triggered by the Azure Web App VS Code extension, which might(??) leverage the Azure CLI (under the hood).

• If your repo is publicly available please share its URL:
  No, it's a private repo.

• What happened?
  See "Situation" section above.

• What did you expect or want to happen?
  I expected the files that the VS Code extension zipped from my DaaS to be successfully unzipped on the container, followed by execution of the default npm start script, which fails because my files were not unzipped.

• How can we reproduce it?
  See "Situation" section above.

• Do you have log output? Please include between the backticks:
  See the 2 code blocks above.