npm ERR! Tracker "idealTree" already exists

Bug Report

• At what date and time did you most recently experience the problem?
  05/04/2024 @ 1:19:12 PM

• Where did you experience the problem? E.g. Azure Web Apps, Azure Functions, Azure Container Registry, or offline use.
  Azure Web Apps

• If your repo is publicly available please share its URL:
  Clone: https://dev.azure.com/jdh7270201/_git/nodejs

• What happened?
  Upon deployment of my repo, onyx threw an error

• What did you expect or want to happen?
  Successful deployment

• How can we reproduce it?
  Unsure. It has occurred across 4 back to back deployments.

• Do you have log output? Please include between the backticks:

Command: oryx build /home/site/repository -o /home/site/wwwroot --platform nodejs --platform-version 20 -p virtualenv_name= --log-file /tmp/build-debug.log  -i /tmp/8dc6c777728a759 -p compress_node_modules=tar-gz | tee /tmp/oryx-build.log
Operation performed by Microsoft Oryx, https://github.com/Microsoft/Oryx
You can report issues at https://github.com/Microsoft/Oryx/issues

Oryx Version: 0.2.20230829.1, Commit: 5bd3088141516cdbd815d62ada052654e91f0429, ReleaseTagName: 20230829.1

Build Operation ID: 976c07f4183fd828
Repository Commit : f306e4b8ac04855bd00832e4e26209ae139b543a
OS Type           : bookworm
Image Type        : githubactions

Detecting platforms...
Detected following platforms:
  nodejs: 20.11.1

Using intermediate directory '/tmp/8dc6c777728a759'.

Copying files to the intermediate directory...
Done in 0 sec(s).

Source directory     : /tmp/8dc6c777728a759
Destination directory: /home/site/wwwroot

Removing existing manifest file
Creating directory for command manifest file if it does not exist
Creating a manifest file...
Node Build Command Manifest file created.

Using Node version:
v20.11.1

Using Npm version:
10.2.4

Running 'npm install'...

npm ERR! Tracker "idealTree" already exists

Start with the supplied Oryx build command and log, focusing on the npm install step with Node 20.11.1 and npm 10.2.4. Compare the deployment environment and repository setup against a reproducible failing deployment; done means identifying a reproducible cause and confirming a successful build.