Removing UV_USE_IO_URING override (#1376)

* Removing `UV_USE_IO_URING` override

This build issue that required these additions ([#1347](heroku/heroku-buildpack-nodejs#1347), [#1351](heroku/heroku-buildpack-nodejs#1351)) was addressed by an upgrade to `kernel-6.1.119-129.201.amzn2023` in [this Amazon Linux AMI release](https://docs.aws.amazon.com/linux/al2023/release-notes/relnotes-2023.6.20241212.html). Therefore, these environment overrides are no longer necessary.

Author: colincasey

CHANGELOG.md

@@ -2,6 +2,7 @@
 
 ## [Unreleased]
 
+- Removed `UV_USE_IO_URING` override. ([#1376](https://github.com/heroku/heroku-buildpack-nodejs/pull/1376))
 
 ## [v281] - 2025-02-05
 

bin/compile

@@ -64,19 +64,6 @@ export PATH="$BUILD_DIR/.heroku/node/bin:$BUILD_DIR/.heroku/yarn/bin":$PATH
 export COREPACK_HOME="$BUILD_DIR/.heroku/corepack"
 export COREPACK_ENABLE_DOWNLOAD_PROMPT=0
 
-# 2024-11-20:
-# We started getting reports on build timeouts on the platform that were unexpected
-# due to the specific versions on Node.js and npm which had been working fine up until
-# this date. After some extensive digging, we believe we narrowed down the cause to
-# a bug in io_uring that affects the Amazon Linux 2023 release. There is a pending fix
-# which will be released around Dec. 9th but, until then, the workaround is set disable
-# the use of io_uring in libuv.
-#
-# See https://github.com/npm/cli/issues/7814#issuecomment-2488626736
-# → https://github.com/amazonlinux/amazon-linux-2023/issues/840#issuecomment-2485782075
-# → https://lore.kernel.org/io-uring/[email protected]/T/#m57570b5f8f2fc00d5a17cfe18ffeeba9fc23a43d
-export UV_USE_IO_URING=${UV_USE_IO_URING:-0}
-
 LOG_FILE=$(mktemp -t node-build-log.XXXXX)
 echo "" > "$LOG_FILE"
 

lib/environment.sh

@@ -108,18 +108,6 @@ write_export() {
     echo "export NODE_HOME=\"$build_dir/.heroku/node\"" >> "$bp_dir/export"
     # shellcheck disable=SC2016
     echo 'export NODE_OPTIONS=${NODE_OPTIONS:-"--max_old_space_size=2560"}' >> "$bp_dir/export"
-
-    # 2024-11-21:
-    # Set UV_USE_IO_URING for later buildpacks to prevent build timeouts when
-    # running `yarn install` on some Amazon Linux 2023 releases. This may be
-    # removed in the future when a fixed AL2023 release is available
-    # (~2024-12-09 or later).
-    #
-    # See https://github.com/npm/cli/issues/7814#issuecomment-2488626736
-    # → https://github.com/amazonlinux/amazon-linux-2023/issues/840#issuecomment-2485782075
-    # → https://lore.kernel.org/io-uring/[email protected]/T/#m57570b5f8f2fc00d5a17cfe18ffeeba9fc23a43d
-    echo 'export UV_USE_IO_URING=${UV_USE_IO_URING:-0}' >> "$bp_dir/export"
-
     # ensure corepack installed binaries are findable by downstream buildpacks
     echo "export COREPACK_HOME=\"$build_dir/.heroku/corepack\"" >> "$bp_dir/export"
   fi

test/fixtures/libuv_io_uring_fix/README.md

@@ -2069,21 +2069,6 @@ testConflictingPackageManagerMetadata() {
   assertCapturedError
 }
 
-testDisableIoUringFix() {
-  compile "libuv_io_uring_fix"
-  assertCaptured "UV_USE_IO_URING is set to 0"
-  assertCapturedSuccess
-}
-
-testDisableIoUringFixUserOverride() {
-  cache_dir=$(mktmpdir)
-  env_dir=$(mktmpdir)
-  echo "1" > "$env_dir/UV_USE_IO_URING"
-  compile "libuv_io_uring_fix" "$cache_dir" "$env_dir"
-  assertCaptured "UV_USE_IO_URING is set to 1"
-  assertCapturedSuccess
-}
-
 # Utils
 
 pushd "$(dirname 0)" >/dev/null