Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't connect to HTTPS URL because the SSL module is not available. when OpenSSL_jll is loaded before Wandb. #39

Closed
lassepe opened this issue Jul 4, 2024 · 4 comments

Comments

@lassepe
Copy link
Contributor

lassepe commented Jul 4, 2024

On a fresh Julia 1.10 install in a clean environment, the reproducer below causes the error:

ERROR: LoadError: Python: CommError: Can't connect to HTTPS URL because the SSL module is not available.

Interestingly, this error only appears when Wandb is loaded after CairoMakie.

using CairoMakie: CairoMakie
using Wandb: Wandb

# trigger ssl error
function provoke_error(logger)
    logging_dict = Dict{String,Any}()
    logging_dict["samples"] = Wandb.Image(CairoMakie.scatter(randn(100)))
    Wandb.log(logger, logging_dict; step=1)
end

logger = Wandb.WandbLogger(; project="test")
provoke_error(logger)
@lassepe
Copy link
Contributor Author

lassepe commented Jul 5, 2024

The offender seems to be OpenSSL_jll. The following will also trigger the issue:

using OpenSSL_jll
using Wandb: Wandb

# trigger ssl error
function provoke_error(logger)
    logging_dict = Dict{String,Any}()
    logging_dict["samples"] = Wandb.Image(rand(2, 2))
    Wandb.log(logger, logging_dict; step=1)
end


logger = Wandb.WandbLogger(; project="test")
provoke_error(logger)

@lassepe lassepe changed the title Can't connect to HTTPS URL because the SSL module is not available. when CairoMakie is loaded before Wandb. Can't connect to HTTPS URL because the SSL module is not available. when OpenSSL_jll is loaded before Wandb. Jul 5, 2024
@lassepe
Copy link
Contributor Author

lassepe commented Jul 5, 2024

Downgrading OpenSSL_jll to v1 seems to fix the issue. I don't think that should be the permanent solution but can be a workaround for now.

@lassepe
Copy link
Contributor Author

lassepe commented Jul 14, 2024

I have opened PR's in the relevant upstream packages:

Given that there's nothing else that we can do here, let me close this one.

@lassepe
Copy link
Contributor Author

lassepe commented Jul 21, 2024

Fixed as per the PRs above

@lassepe lassepe closed this as completed Jul 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant