ugexe / zef

Raku Module Management
Artistic License 2.0
207 stars 44 forks source link

Module installation fails on Windows 11 #567

Open wbiker opened 4 weeks ago

wbiker commented 4 weeks ago

IO::Prompt installation works fine on Linux, but fails on Windows 11 because of a type check fail. Not sure if it this is the right place, but the error does not mean anything to me. The Str/CompUnit issue might point to a too old version. But all installation are max 3 month old.

Context

Only on Windows 11 installation fails to bind the $repo-id parameter/

Expected Behavior

zef installs IO::Prompt. Test works fine

Actual Behavior

Installation fails during compiling [IO::Prompt] 022efd3a.tar.gz\dist/t\01-simple.rakutest: ===> Searching for: IO::Prompt ===> Staging IO::Prompt:ver<0.0.3>:auth ===> Staging [OK] for IO::Prompt:ver<0.0.3>:auth ===> Testing: IO::Prompt:ver<0.0.3>:auth [IO::Prompt] ===SORRY!=== Error while compiling C:\Users\test\AppData\Local\Temp.zef\1723616685.912\ef587aec4aed2db06d9d8049a0398dbe [IO::Prompt] 022efd3a.tar.gz\dist/t\01-simple.rakutest [IO::Prompt] Type check failed in binding to parameter '$repo-id'; expected Str but got CompUnit::Repository::Spec [IO::Prompt] (CompUnit::Repository...) [IO::Prompt] at C:\Users\test\AppData\Local\Temp.zef\1723616685.912\ef587aec4aed2db06d9d [IO::Prompt] 8049a0398dbe022efd3a.tar.gz\dist/t\01-simple.rakutest:1 ===> Testing [FAIL]: IO::Prompt:ver<0.0.3>:auth

Steps to Reproduce

Just try to install IO::Prompt on the Windows 11 version mentioned below.

Your Environment

Raku Star v2024.05 zef --version: 0.22.0 Windows 11: 23H2 (OS Build 22631.3880) PowerShell 7.4.4

ugexe commented 4 weeks ago

See: https://github.com/rakudo/rakudo/issues/5615

ugexe commented 4 weeks ago

Could you see if it happens if you set MVM_SPESH_DISABLE=1?

ugexe commented 4 weeks ago

zef install IO::Prompt succeeded for me with Windows 11 on rakudo 2023.04 (and I can't build a newer one in this VM)

wbiker commented 3 weeks ago

With MVM_SPESH_DISABLE=1 still reporducable. The same issue. I also tried it with the cmd.exe instead of powershell to see if there is a difference, but no luck