Update duckdb-wasm to latest

[jzavala-gonzalez]

Is your feature request related to a problem? Please describe.
I'm writing a notebook that uses the native Observable DuckDB client. One query attempts using DuckDB's UNPIVOT statement introduced in DuckDB 0.8.0 (released around mid-May 2023, see announcement and docs). The query fails with a syntax error (see screenshot) which I'm guessing is due to an outdated duckdb-wasm version in Observable. Checking the stdlib dependencies file shows Observable is using version 1.24.0 of duckdb-wasm, which was published in March according to npm. That months-long difference between 1.24.0 and 1.27.0 could explain why UNPIVOT isn't working within yet Observable.

Describe the solution you'd like
Update to the latest version of duckdb-wasm, which at time of writing is 1.27.0 and was published mid-June.

Describe alternatives you've considered
If updating isn't possible, one could update the intro notebook "Hello, DuckDB" to mention what version of duckdb Observable is currently running so users can look at the correct documentation.

Additional context

[mbostock]

Related observablehq/stdlib#364 observablehq/stdlib#378

We ran into backwards incompatibility issues last time we upgraded, but someone simply needs to test the latest version of duckdb-wasm (currently 1.27.0) and then we can upgrade.

[jzavala-gonzalez]

Thank you for the quick response and merge!! I'm still getting the syntax error but I haven't been able to check whether the update has activated on the notebook (or what version of the stdlib and runtime it's using). Is the update immediate? I can check over the next few days if it changes or check if I just have a bug in the query.

[mbostock]

Hasn’t quite landed yet! It should be available this week though. We will give an update here when it is released.

[annie]

hey @jzavala-gonzalez, we just deployed the update and i see UNPIVOT working in production now. let us know if it's working for you!

[jzavala-gonzalez]

It's working!! I can finish the notebook now. Thank you so much!! In case there's interest here's the (in-progress) link: https://observablehq.com/@jzavala-gonzalez/am4-scalable-time-series-visualization It's a fork of UW Data's implementation of the M4 algorithm so it adjusts into AM4. The algorithm is very SQL friendly so UNPIVOT really helps wrap it together as the last step before plotting. Thank you! Closing the issue

[annie]

unfortunately the upgrade seems to have created some issues with the DuckDB client on Safari, so we just had to revert it. sorry for the churn, we will work on getting a fix in and re-applying the upgrade ASAP! i'll reopen the issue for now.

[jzavala-gonzalez]

Ok! Take the time you need. I had the chance to actually finish the notebook while the update was out so I already know it should all work once the update is back up. So no rush from my part. Thank you!!

[tophtucker]

To summarize a little more:

• It looks like duckdb-wasm 1.25.0 introduces the issue.
• This notebook reproduces the error: in Safari and Firefox, loading a sufficiently large CSV from S3 (i.e. a file attachment if you refresh after uploading) into DuckDB fails with a range request error. movies.csv (439 KB) fails; penguins.csv (14 KB) doesn’t.
• There’s a config option, allowFullHTTPReads, which looked like it might help, but either it didn’t or I don’t understand.

We’re investigating; I also opened an issue on duckdb-wasm, in case they spot or know anything else.

[carlopi]

Hi all, Carlo here, from DuckDB team.

We would really like to see duckdb-wasm bumped, and I am available to help, but I think in this case there is something off with either the S3 setting or with the CDN settings when range request are made passing "Accept-Encoding" parameter (this is automatically handled by the browser, see: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept-Encoding).

Could someone take a look at these simple curl examples: duckdb/duckdb-wasm#1366 (comment). I believe fixing the responses in those cases (that is, NOT advertising something as compressed blindly but only when actually compressed) would solve the issue you are seeing.