New version Installation Issue

Installation
1

Hello!

I have an issue regarding the installation of the new version of Pumas, For some reason, the new version is failing to install in the laptop. I tried installing via the VSCOde extension and the manual install as you see below, but I still get the same error message.

ERROR: failed process: Process(julia +1.11.8 --startup-file=no '--project=C:\Users\haric\AppData\Local\Temp\jl_dlET0T' 'C:\Users\haric\AppData\Local\Temp\jl_sFkmNP\install.jl', ProcessExited(1)) [1]

Stacktrace:[1] pipeline_error@ .\process.jl:598 [inlined][2] run(::Cmd; wait::Bool)@ Base .\process.jl:513[3] run@ .\process.jl:510 [inlined][4] (::PumasProductManager.var"#4#7"{String, Vector{Dict{String, String}}, String})(tmp::String)@ PumasProductManager C:\Users\haric.julia\packages\PumasProductManager\BtnsT\src\PumasProductManager.jl:377[5] mktempdir(fn::PumasProductManager.var"#4#7"{String, Vector{Dict{String, String}}, String}, parent::String; prefix::String)@ Base.Filesystem .\file.jl:819[6] mktempdir (repeats 2 times)@ .\file.jl:815 [inlined][7] _pkg_add_operations@ C:\Users\haric.julia\packages\PumasProductManager\BtnsT\src\PumasProductManager.jl:344 [inlined][8] (::PumasProductManager.var"#2#3"{String, String, Vector{Dict{String, String}}, Dict{String, Any}, String})(dir::String)@ PumasProductManager C:\Users\haric.julia\packages\PumasProductManager\BtnsT\src\PumasProductManager.jl:294[9] mktempdir(fn::PumasProductManager.var"#2#3"{String, String, Vector{Dict{String, String}}, Dict{String, Any}, String}, parent::String; prefix::String)@ Base.Filesystem .\file.jl:819[10] mktempdir(fn::Function, parent::String)@ Base.Filesystem .\file.jl:815[11] mktempdir@ .\file.jl:815 [inlined][12] install(env::String, dst::String; force::Bool)@ PumasProductManager C:\Users\haric.julia\packages\PumasProductManager\BtnsT\src\PumasProductManager.jl:277[13] install@ C:\Users\haric.julia\packages\PumasProductManager\BtnsT\src\PumasProductManager.jl:255 [inlined][14] init(product::String, path::Nothing)@ PumasProductManager C:\Users\haric.julia\packages\PumasProductManager\BtnsT\src\PumasProductManager.jl:252[15] init(product::String)@ PumasProductManager C:\Users\haric.julia\packages\PumasProductManager\BtnsT\src\PumasProductManager.jl:216[16] do_cmd(command::Pkg.REPLMode.Command, io::Base.TTY)@ Pkg.REPLMode C:\Users\haric.julia\juliaup\julia-1.11.8+0.x64.w64.mingw32\share\julia\stdlib\v1.11\Pkg\src\REPLMode\REPLMode.jl:404[17] do_cmds(commands::Vector{Pkg.REPLMode.Command}, io::Base.TTY)@ Pkg.REPLMode C:\Users\haric.julia\juliaup\julia-1.11.8+0.x64.w64.mingw32\share\julia\stdlib\v1.11\Pkg\src\REPLMode\REPLMode.jl:393[18] do_cmds(repl::REPL.LineEditREPL, commands::String)@ REPLExt C:\Users\haric.julia\juliaup\julia-1.11.8+0.x64.w64.mingw32\share\julia\stdlib\v1.11\Pkg\ext\REPLExt\REPLExt.jl:92[19] on_done(s::REPL.LineEdit.MIState, buf::IOBuffer, ok::Bool, repl::REPL.LineEditREPL)@ REPLExt C:\Users\haric.julia\juliaup\julia-1.11.8+0.x64.w64.mingw32\share\julia\stdlib\v1.11\Pkg\ext\REPLExt\REPLExt.jl:106[20] #invokelatest#2@ .\essentials.jl:1055 [inlined][21] invokelatest@ .\essentials.jl:1052 [inlined][22] (::REPLExt.var"#47#50"{REPL.LineEditREPL})(s::REPL.LineEdit.MIState, buf::IOBuffer, ok::Bool)@ REPLExt C:\Users\haric.julia\juliaup\julia-1.11.8+0.x64.w64.mingw32\share\julia\stdlib\v1.11\Pkg\ext\REPLExt\REPLExt.jl:128[23] #invokelatest#2@ .\essentials.jl:1055 [inlined][24] invokelatest@ .\essentials.jl:1052 [inlined][25] run_interface(terminal::REPL.Terminals.TextTerminal, m::REPL.LineEdit.ModalInterface, s::REPL.LineEdit.MIState)@ REPL.LineEdit C:\Users\haric.julia\juliaup\julia-1.11.8+0.x64.w64.mingw32\share\julia\stdlib\v1.11\REPL\src\LineEdit.jl:2755[26] run_frontend(repl::REPL.LineEditREPL, backend::REPL.REPLBackendRef)@ REPL C:\Users\haric.julia\juliaup\julia-1.11.8+0.x64.w64.mingw32\share\julia\stdlib\v1.11\REPL\src\REPL.jl:1508[27] (::REPL.var"#79#85"{REPL.LineEditREPL, REPL.REPLBackendRef})()@ REPL C:\Users\haric.julia\juliaup\julia-1.11.8+0.x64.w64.mingw32\share\julia\stdlib\v1.11\REPL\src\REPL.jl:497
2

Hello,

I tried reinstalling the version 2.7.1, and it worked. However, I’m still unable to install versions 2.8.0 and 2.8.1.

3

Hello @HariV,

Is there any logging appearing above the error log that you’ve shown here?

Kind regards,
Michael Hatherly

4

Hello!

No, I don’t seem to see any logging before the error log.

Thank you,
With Regards,
Hari Chandana. V

5

Hi @HariV,

See if you can scroll up in the terminal buffer. There definitely should be more content above what you’ve pasted in here. If you’re not able to scroll up please provide a screenshot of the vscode (hiding any sensitive info of course). Also provide the version of the Pumas VSCode extension that you are on.

Kind regards,
Michael

6

Title: Had a rough time installing Pumas/DeepPumas on Apple Silicon Mac

Hey everyone,

Just wanted to share some installation pain I ran into on a new M-series Mac in case it helps others (or the team).

I did a full factory reset on my Mac recently and was trying to get both Pumas 2.8.1 and DeepPumas 0.10.0 installed cleanly. Used the VS Code extension first, then fell back to the manual product manager route through Terminal.

The product manager kept trying to install the x64 version of Julia 1.11.8 even though this is an aarch64 machine. That made the juliaup launcher crash every time. I also had issues because my default Julia was 1.12 (had to switch to 1.11 to even get past the package resolution errors).

The VS Code extension wasn’t much help either. It just said the install failed and the terminal was empty, so I had to do everything from a regular terminal and manually link the aarch64 binary so the product manager would stop asking for the Intel one.

Eventually got both working, but it took quite longer than it should have. Is the Apple Silicon support still a bit incomplete on the installer side, or did I just hit a weird situation case after the factory reset?

Thanks,

Bilal

7

Hi @BTariq,

Apple Silicon support for Pumas 2.8.1 should be fine. Could you please provide some of the actual error messages that you encountered while trying to get installed and that will help us diagnose what the issues were?

Kind regards,
Michael