Windows CI for the Julia Pkg errors with 'Could not load symbol "duckdb_vector_size"'

[abelsiqueira]

What happens?

We have a failing Julia package build with DuckDB_jll 1.1.0 for Windows GitHub runners: https://github.com/TulipaEnergy/TulipaEnergyModel.jl/actions/runs/10833112611/job/30062514253

Revelant part reproduced:

ERROR: LoadError: could not load symbol "duckdb_vector_size":
The specified procedure could not be found. 

I saw other failures on 1.1.0, but I couldn't tell if they were related to this issue or not.

To Reproduce

I created a simple repo building a Julia package that runs DuckDB here: https://github.com/abelsiqueira/DuckDBDebug.jl/actions/runs/10835456425/job/30067028887

You can see:

• It passes for ubuntu on DuckDB_jll 1.0.0 and 1.1.0
• It passes for Windows on DuckDB_jll 1.0.0
• It fails for Windows on DuckDB_jll 1.1.0

The code is very simple, and it doesn't actually run, since it fails on precompilation, but everything is included in the repo (https://github.com/abelsiqueira/DuckDBDebug.jl).

OS:

windows-latest on CII

DuckDB Version:

1.1.0

DuckDB Client:

Julia

Hardware:

No response

Full Name:

Abel Soares Siqueira

Affiliation:

Netherlands eScience Center

What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.

I have tested with a stable release

Did you include all relevant data sets for reproducing the issue?

Yes

Did you include all code required to reproduce the issue?

• Yes, I have

Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?

• Yes, I have

[ansaardollie]

I am having the same issue, just got a new laptop and did a fresh install of Julia, tried adding the package and this error prevented the package from precompiling.

[szarnyasg]

Hi @abelsiqueira and @ansaardollie, thanks for opening this issue and joining the discussion. The DuckDB Julia API is experimental and not covered by community support. We welcome contributions fixing this issue but the core team is unlikely to fix this bug in the near future.

[abelsiqueira]

Thanks for the reply @szarnyasg. Just an update on our side, DuckDB_jll@v1.1.0 is broken on local Windows machines as well, not just the CI.

Maybe limiting the DuckDB dependency on DuckDB_jll to =1.0.0 is a workaround until it's fixed.

For other users, you can add and pin DuckDB_jll to v1.0.0 with

pkg> add DuckDB_jll@v1.0.0
pkg> pin DuckDB_jll@v1.0.0

Since DuckDB compat bounds include DuckDB_jll 1.1.0, then you either do that or pin DuckDB itself to v0.10.3.

[szarnyasg]

Thanks for the additional info, this definitely warrants a look on our side.

[Mytherin]

Does this issue still persist with DuckDB 1.1, or is this issue specifically about using DuckDB 1.0 in combination with DuckDB_jll 1.1?

[abelsiqueira]

It was about DuckDB.jl 1.0 with jll 1.1, because DuckDB.jl 1.1.0 was not around yet. But I reran the tests in https://github.com/abelsiqueira/DuckDBDebug.jl/actions/runs/10835456425/job/30067028887 and they also fail with DuckDB.jl 1.1.0

[abelsiqueira]

I'm on the phone hope this is the link: https://github.com/abelsiqueira/DuckDBDebug.jl/actions/runs/10835456425/job/30358662742#step:8:56

[jhmenke]

I can confirm this issue on a number of different Windows 10 computers.

I guess the Windows libduckdb is not compiled correctly. A temporary fix was:

[compat]
DuckDB_jll = "=1.0.0"

in the Project.toml

[abelsiqueira]

Maybe version 1.1.1 fixes the issue? Can we have new DuckDB_jll and DuckDB.jl releases?

[mzy2240]

Still an issue in Windows