Closed bhatiaabhinav closed 2 years ago
Figured that wandb.init()
is causing the problem when trying to create the wandb process. On Windows, adding the argument settings=wandb.Settings(start_method="thread")
to the wand.init()
call solves the problem.
To pass that argument via WandbLogger
constructor, one would need to do:
using PyCall
@pyimport wandb
lg = WandbLogger(project = "Wandb.jl", name = nothing, settings=wandb.Settings(start_method="thread"))
@avik-pal The problem is happening again. You undid the fix?
This is happening even with explicitly passing the settings
kwarg? (I don't have a Windows machine to test)
@bhatiaabhinav can you try https://github.com/avik-pal/Wandb.jl/pull/5?
I didn't check with explicit kwarg. But I thought you had already made it by default to spawn wandb as a new thread instead of a new process. Maybe I misunderstood.
So if you recommend that we should pass the kwarg explicitly (when on Windows), it would be helpful if you document it in the Readme.
try #5 how?
Ah you want me to test that new branch. Ok let me try.
@avik-pal Yeah it works fine. The pull request looks good to go!
Awesome registered a patch release https://github.com/JuliaRegistries/General/pull/49852
I have Julia 1.6.2 installed on Windows 11. I am using Miniconda for PyCall.
I am getting the following error on invoking WandbLogger constructor.
At that point, the interpreter freezes. Everything runs fine on Ubuntu though.