Discrepancies with CLI DuckDB

[amir20]

I have noticed that using duckdb-wasm with the following JSON

{"m":"192.168.215.1 - - [27/Aug/2024:20:58:40 +0000] \u0026#34;GET /v2/_catalog?n=1000 HTTP/1.1\u0026#34; 200 20 \u0026#34;\u0026#34; \u0026#34;curl/8.7.1\u0026#34;","ts":1724792320349,"id":2133532589,"s":"stdout","c":"9da1a8d03a8a"}
{"m":{"time":"2024-08-27T21:15:14.450092541Z","level":"info","msg":"PurgeUploads starting: olderThan=2024-08-20 21:15:14.449212711 +0000 UTC m=-603779.987243667, actuallyDelete=true"},"ts":1724793314453,"id":478436634,"l":"info","s":"stderr","c":"9da1a8d03a8a"}

Notice that some times m is JSON and sometimes just string.

I run with

const response = await fetch("http://192.168.68.66:8080/logs.json");

    if (!response.ok) {
      throw new Error(`Failed to fetch logs: ${response.statusText}`);
    }

    await db.registerFileBuffer("logs.json", new Uint8Array(await response.arrayBuffer()));

    const conn = await db.connect();
    const results = await conn.query(`
      SELECT * FROM logs.json
      `);

    for (const row of results.toArray()) {
      console.log(row.m.time);
    }

Unfortunately, m is always string even when it should be parsed as JSON.

The same file with cat logs.json | duckdb -c "SELECT m.time FROM read_json('/dev/stdin')" seems to work though.

I am not sure why this is happening. Anybody have an idea?