Question about fix timeline for DuckDB-WASM remote Parquet partial loading regression with presigned URLs

[missserious]

Title:
Remote Parquet partial loading regression in DuckDB-WASM with presigned URLs - fix timeline?

Body:

Dear DuckDB team,

I am currently using DuckDB-WASM in a web application to query remote GeoParquet files directly from object storage.

I noticed that the regression affecting remote Parquet partial loading in newer DuckDB-WASM versions is already known from existing issues.

For my use case, @duckdb/duckdb-wasm version 1.29.0 is currently the latest version that works reliably. Newer versions affect the partial loading behaviour, which is important for our application because we rely on HTTP Range Requests to efficiently query large remote Parquet files.

I have also tested the latest development version, but the partial loading behaviour does not appear to be fixed there yet.

I wanted to ask:

• Is there already an ongoing effort to fix this issue?
• Is there an estimated target version or timeline for a fix?
• Would you recommend staying on 1.29.0 until the fix is released?

Our setup:

• DuckDB-WASM: 1.29.0 (working)
• Tested versions: newer releases and latest development version
• Data format: GeoParquet
• Remote Parquet files (~100–400 MB)
• Storage: S3-compatible object storage
• Access: HTTPS via presigned URLs
• HTTP Range Requests enabled
• Browser-based querying
• Query pattern: filtering rows by pid

The same setup is used when comparing different DuckDB-WASM versions.

With v1.29.0, the same files and queries correctly use HTTP Range Requests and only fetch the required byte ranges.

Observed behaviour with newer versions:

Instead of using HTTP Range Requests to load only the required parts of the Parquet file, the complete Parquet file is loaded as a bulk download.

Has anyone else observed similar behaviour, or is there an expected timeline for a fix?

I would be happy to provide a minimal reproduction example or additional details if this helps. Also I would be happy to help with testing potential fixes or provide feedback on development versions if that would be useful.

Thanks a lot for your work on DuckDB-WASM.

Thank you so much! 💚