vim.uv.os_uname().info.machine returns 'unknown' for Windows ARM CPU

[zachbugay]

Problem

When running Neovim with Windows OS on a ARM Processor, the machine info is unknown.

vim.uv.os_uname().info.machine
Steps to reproduce
Install Neovim (nightly or stable) on running Windows with an ARM Processor.

I have tried to install luv via luarocks but it is failing to build. I am not actually able to run luv and run uv.os_uname().

-- init.lua
vim.print(vim.uv.os_uname())
Expected behavior
machine should have the correct value

Nvim version (nvim -v)
v0.12.0-dev-1998+g272ec9627c

Operating system/version
Windows 11

Terminal name/version
Windows Terminal 1.23.13403.0

$TERM environment variable
n/a

Installation
scoop install neovim-nightly

I opened an issue on Neovim, but this looks to be an issue with luv and not neovim.

[truemedian]

Luv does not handle os_uname specially, whatever string Libuv provides from uv_os_uname is provided verbatim.

This sounds like an upstream issue that needs to be addressed in Libuv.

This is probably addressed by libuv/libuv@917c1ad, but there has not been a Libuv release since this commit.