bnonce

Results 3 issues of bnonce

We've a case where coroot-node-agent (logparser) accidentally merges multiple json logs into one but we expect to receive them one-by-one. Output: ``` {"context":"App:TypeOrmTransactionContext","level":"debug","timestamp":"2024-02-21T12:35:48.232Z","ms":"+1ms","span_id":"2aa1bcfe9bc837f2","trace_id":"1167fdf089bce248aa87fddee93eedff","msg":"..."} {"context":"App:TypeOrmTransactionContext","level":"debug","timestamp":"2024-02-21T12:35:48.239Z","ms":"+7ms","span_id":"2aa1bcfe9bc837f2","trace_id":"1167fdf089bce248aa87fddee93eedff","msg":"..."} {"context":"App:TypeOrmTransactionContext","level":"debug","timestamp":"2024-02-21T12:35:48.239Z","ms":"+0ms","span_id":"2aa1bcfe9bc837f2","trace_id":"1167fdf089bce248aa87fddee93eedff","msg":"..."} ``` We fixed this issue...

Bun version: v1.2.3 We must make a copy [here](https://github.com/uptrace/bun/blob/760de7d0fad15dc761475670a4dde056aef9210d/model_map.go#L85) ​​taking into account the [doc](https://github.com/golang/go/blob/master/src/database/sql/sql.go#L451). Now select is broken and can return invalid data.