Dolan Murvihill

I have on my fork a [minimum working example](https://github.com/direct-democracy-solutions/node-csv/tree/transform-memory-leak) of this bug. It looks like the transform is breaking Node's built-in backpressure logic by ignoring the return value from `push`....

Still not working on my repro: ```javascript import {transform} from 'stream-transform'; import {pipeline, Readable, Writable} from "stream"; class DummyData extends Readable { constructor() { super(); this.numReads = 0; } _read()...

Hey, thanks for being so attentive to this issue! It looks like that does respect backpressure and pause the stream, but how does it get unpaused?

Consider allowing `cancel()` to just accept the original `Promise` back directly and finding it with `===`. It would require a linear scan of the entire queue (worst case), but that's...

> Hey folks, thank you very much for this issue and the related discussion. We discussed this issue in the core team and feel that the majority of the use...

> Hi @dmurvihill we discussed your comment with the core team and the main problem is that this would require a protocol change to implement. Currently, providers are allowed to...

+1 for this, I'm trying to use with `jest-mock-axios` and having trouble resetting the mock between tests.

I think there is [other software](https://www.postgresql.org/) that might be better suited for this use case.

Here's my Compose file. The `db` container starts the db and the `migrate` container runs the migrations. Not tested with docker-in-docker, so YMMV. ```yml db: image: 'postgres:15.3-alpine3.18' ports: - '5432:5432'...

No thanks, this is three steps upstream from me and my direct dependency already migrated away. I could do a one-time look at the straightforward PRs that are open today,...