SET force_download = true in error

[ericemc3]

What happens?

with shell.duckdb.org

INTERNAL Error: Invalid PhysicalType for GetTypeIdSize
This error signals an assertion failure within DuckDB. This usually occurs due to unexpected conditions or errors in the program's logic.

To Reproduce

SET force_download = true ;

Browser/Environment:

Chrome, firefox...

Device:

pc win11

DuckDB-Wasm Version:

1.29.1

DuckDB-Wasm Deployment:

shell.duckdb.org

Full Name:

eric mauviere

Affiliation:

icem7

[Achavezrdz1]

win11

[carlopi]

Thanks for the report, I think there are two sides of the fix: one is duckdb/duckdb#18353, where we need more robustness when the set of exported setting from an extension changes, and the second is removing custom code in httpfs compiled to wasm (for that I have not a PR up yet).

[bhvngt]

Just checking if there is any update on this issue. I am seeing the same issue with duckdb-wasm.

[carlopi]

Thanks for raising, again.

This is connected to custom handling of httpfs extension in wasm. If you switch that off, via SET builtin_httpfs = false;, httpfs is then properly autoloaded and this should work.

SET builtin_httpfs = false;

has wide reaching consequences, mostly positive one since secrets and HTTP stack will be more aligned to native duckdb HTTP stack.

I am collecting this issues, will keep them open until we will actually revert the default so that this works out of the box.

[bhvngt]

Thanks @carlopi for your explanation.

I tried setting force_download to avoid HEAD call while fetching protected data on the browser using secrets. Here's the snapshot of same set of call on CLI and on the browser

Browser Session

CLI session

After setting force_download httpfs still makes HEAD call in the browser. So force_download does not appear to be working on the browser after disabling builtin httpfs

[carlopi]

Thanks for checking, I'll come back, I think I have a clue of what is going wrong.