Intermittent Error Loading Parquet Extension

[archiewood]

What happens?

When loading DuckDB inside Evidence, intermittently getting a 404 from the parquet extension URL:

This can typically be fixed by a hard reload.

It seems like the endpoint might be occasionally failing to serve the extension?

An error occurred while trying to automatically load the required extension 'parquet': Extension https://extensions.duckdb.org/v1.1.1/wasm_eh/parquet.duckdb_extension.wasm is not available.

To Reproduce

Occurs during the load process, so cannot run SQL.

Browser/Environment:

Chrome XXX

Device:

MacOS

DuckDB-Wasm Version:

1.29.0

DuckDB-Wasm Deployment:

Evidence

Full Name:

Archie Sarre Wood

Affiliation:

Evidence

[zachstence]

This was caused by the URL https://extensions.duckdb.org/v1.1.1/wasm_eh/parquet.duckdb_extension.wasm returning a 404. A refresh of the browser fixed it (the request returned a 200).

We've seen this very intermittently, just once a week or so

[carlopi]

Thanks for raising.

Retry mechanism to handle this problems has been added to duckdb native, I had assumed browsers are good enough to handle this, but this the returned 404 do not help.

I need to check whether this can be solved at the level of the served file or just add redundancy with a retry mechanism in duckdb-wasm.

Idea could be doing something like:

• https://extensions.duckdb.org/v1.1.1/wasm_eh/parquet.duckdb_extension.wasm
• https://extensions.duckdb.org/v1.1.1/wasm_eh/parquet.duckdb_extension.wasm?1
• https://extensions.duckdb.org/v1.1.1/wasm_eh/parquet.duckdb_extension.wasm?2
• actual failure