Elliana May

@ankoh there doesn't seem to be much in the way of build instructions anywhere, should i be doing `make wasm_debug js_debug` or somesuch?

Okay, progress! ```sh Jul 26, 01:04:50 PM: 24790052 ERROR Error [RuntimeError]: Aborted(native code called abort()) at T (/var/task/api/duckdb-wasm/duckdb-node-mvp.worker.cjs:2:118142) at zl (/var/task/api/duckdb-wasm/duckdb-node-mvp.worker.cjs:3:9424) at kh (/var/task/api/duckdb-wasm/duckdb-node-mvp.worker.cjs:4:19638) at std::__terminate(void (*)()) (wasm://wasm/0c1fe5de:wasm-function[332]:0x35ed6) at std::terminate()...

Yep, that seems to work fine - are there docs describing how I'm supposed to be opening on disk databases with duckdb-wasm?

@ankoh what exactly should I be passing for the handle? The path to the file? (The parameter is very weakly typed)

Okay, using `registerFileBuffer` I'm able to read the parquet file fine (see https://duckdb-website-search.netlify.app/.netlify/functions/short and https://github.com/Mause/duckdb_website_search/blob/main/api/short.ts) Trying to do the same with the database gives me a read-only filesystem error (see...

Okay, in the end I was able to make this work using that method, but only after copying it to the `/tmp` filesystem, to work around the readonly filesystem error

Are you able to see what the actual response is in the network tab in your browsers devtools? You might be actually getting an auth error, for example

@hustnn as you can see in the screenshot, your actual issue is an authentication one. I would suggest making sure your aws credentials can actually access that s3 bucket

Perhaps verify that the headers being sent are the expected ones in the network console? And that you have declared those headers correctly in your S3 CORS config?

@jcubic are you able to give some direction as to where the code should be added? Right now I'm just patching the commit objects returned by the api