gcs: Bump to 0.0.4

[russellhancox]

Also: re-enable Windows builds

[taniabogatsch]

Hi - I restarted the Windows run now since it seems spurious. But if it fails again it might need more thorough investigation. 👍

[russellhancox]

This still appears to be failing but I'm a little at a loss as to why, the same build worked fine in our extension repo: https://github.com/northpolesec/duckdb-gcs/actions/runs/22139297199/job/64015425496. A cursory search suggests the error is related to input paths being too long.

[brokenjacobs]

I don't know if this helps but I looked through the build logs and there is a slight version mismatch, this failing PR says:

Visual Studio 2022 Developer Command Prompt v17.14.26

but the working PR from the extension repo says:

Visual Studio 2022 Developer Command Prompt v17.14.25

on the build step.

[carlopi]

There was some instability on CI, that I think it's fixed in main.

I took the liberty of rebasing the PR onto duckdb/community-extensions main branch, let's see what CI says.

[fb64]

Thanks @carlopi, could you try using the latest commit 9d2cb749affdebef8f4c0c78e21683bc9f5e2c0f with the updated submodule (1.4.4). I hope this resolves ix the build issue 🙏

[fb64]

The build has used the latest version (1.5.0)...According to the build script, to use the v1.4 duckdb_version property should be set to v1.4.4 instead of v1.4.2 in the MainDistributionPipeline
(If I understood correctly 🤔)

[fb64]

🤞

[fb64]

The upgrade to DuckDB v1.5.0 has been done and the build was successfull for the on both my fork branch and on the main branch of the extension repository 🤔
Any help would be appreciate to fix this build issue @carlopi @taniabogatsch 🙏

[carlopi]

Restarted Windows CI, let's see.

[fb64]

Thanks, @carlopi but still fail ... It's possible to get the following log file from the build : D:\a\community-extensions\community-extensions\vcpkg\buildtrees\google-cloud-cpp\install-x64-windows-static-release-rel-out.log or re-run windows build in debug mode ?
It could be a cache issue or something else ? Are the build tools the same as extension-ci-tools ?

[fb64]

After reviewing logs, It seems that in the community-extensions build an external ninja version 1.12.1 instead of 1.13.2 is used to install vcpkg package : -- Found external ninja('1.12.1'). and this log is not present in the main branch build of the extension repository 🤔
The rest seems to match : vcpkg packages version, MSVC compiler versions (19.44.35223.0) etc ...
I'm no expert in C++ compilation, and even less so on the Windows platform, but this is the only clue I've found.

[carlopi]

I am trying to debug the issue, opened a PR at #1536 to double check the results.