Carlos Fuentes
Carlos Fuentes
>connections `connections` does only applies to high level APIs like Agents/Pools, for low level ones like `Clients` this is of no help as each Client/Dispatcher maps to a single socket....
What would be the shape of it, and its considerations? From what I've seen from the issue shared by @aduh95 the main security points seem valid; Chromium seems to have...
@ronag Sure, if you can Tomorrow lets do it. Just drop me a message on Slack. i also notice some issues now that you asked for the deleteRecord
It would be nice, shall we do this right away (given that `node:sqlite` is experimental) or enable/disable it somehow through a flag and mark it as experimental?
>I have considered creating a separate MockAgent instance for every test case, but I'm not sure it's a good idea since it can have a performance overhead and a lof...
Contributions are welcomed! Happy to support with guidance for landing this
This [dispatcher handlers](https://undici.nodejs.org/#/docs/api/Dispatcher?id=parameter-dispatchhandler) will start receiving the `headers` already parsed instead of in a Buffer format, isn't it?
Will check the H2 issues throughout the day
I don't believe they are flaky as they are pretty consistent across jobs: https://github.com/nodejs/undici/actions/runs/9980661941/job/27582582584?pr=3408#step:8:2242 Seems to be related with `fetch` and parsing non-Latin1 chars on headers.
It seems CI is still not happy...