HTTP logging is not working while using duckdb-wasm

[bhvngt]

What happens?

I am not able to view http logs while using duckdb wasm. I tried to print them from duckdb_logs_parsed('HTTP') macro after setting required configurations (those that works with duckdb cli);

To Reproduce

When I execute following command

PRAGMA enable_logging('HTTP');
SET enable_http_logging = true;
SET logging_storage = memory;
SELECT * FROM read_json('https://dummyjson.com/products/1');
SELECT request.type FROM duckdb_logs_parsed('HTTP');

duckdb cli prints following http log.

However, while running the same command on DuckDb Shell, I get empty output.

Am I missing something here? Thanks in advance.

Browser/Environment:

chrome v139

Device:

Macbook

DuckDB-Wasm Version:

v1.3.2

DuckDB-Wasm Deployment:

https://shell.duckdb.org/

Full Name:

Bhavin Kamani

Affiliation:

Freelance Developer from India

[ShravanSunder]

I'm also getting the same problem for any duckdb_logs

call enable_logging(level='info'); or SET enable_logging = true;

// --> any sql here

select * from duckdb_logs();

[ShravanSunder]

here's a detailed example using 1.4

CALL enable_logging(['QueryLog'], storage='memory', storage_buffer_size=0);
CALL truncate_duckdb_logs();

CREATE OR REPLACE TABLE t(id INTEGER);

BEGIN;
INSERT INTO t VALUES (1);
ROLLBACK;

SELECT type, message FROM duckdb_logs ORDER BY timestamp;
SELECT * FROM t;

in shell

in cli

[carlopi]

Thanks for raising, this is indeed quite off, I will need to check and come back on this.

[carlopi]

After looking at this, I did have found some unclear behaviour, BUT this can also work, see:
https://shell.duckdb.org/#queries=v0,CALL-enable_logging(%5B'QueryLog'%5D%2C-storage%3D'memory'%2C-storage_buffer_size%3D0)~CALL-truncate_duckdb_logs()~CREATE-OR-REPLACE-TABLE-t(id-INTEGER)~BEGIN~-INSERT-INTO-t-VALUES(1)~-ROLLBACK~SELECT-type%2Cmessage-FROM-duckdb_logs-ORDER-BY-timestamp~,-FROM-duckdb_logs()-SELECT-COLUMNS(*)%3A%3AVARCHAR~

[carlopi]

ROLLBACK: this does work as intended, BUT it's the shell rendering that is not handling this correctly, see https://shell.duckdb.org/#queries=v0,CALL-enable_logging(%5B'QueryLog'%5D%2C-storage%3D'memory'%2C-storage_buffer_size%3D0)~CALL-truncate_duckdb_logs()~CREATE-OR-REPLACE-TABLE-t(id-INTEGER)~BEGIN~-INSERT-INTO-t-VALUES(1)~-ROLLBACK~SELECT-type%2Cmessage-FROM-duckdb_logs-ORDER-BY-timestamp~,-FROM-duckdb_logs()-SELECT-COLUMNS(*)%3A%3AVARCHAR~

[ShravanSunder]

I tried out your examples, it looks like it works.

[carlopi]

The main example, around HTTP logging still has something off, I would need to check what's the diff there, I would fix and come back

[bhvngt]

Yes. Sql logging is working. However, http logging is not working;

Thanks @carlopi for looking into this

[carlopi]

It's not completely solved, but mostly, see PR message at #2103

Thanks for raising!!

[bhvngt]

@carlopi Thanks for the fix.

I could not make it work on the @duckdb/duckdb-wasm@1.30.1-dev3.0. I am guessing that the fix will be available on the next dev version.

I am also facing #2048. When I disable builtin_httpfs. force_download stops throwing any error. Is this also a possible fix for #2048 issue?