Steven Roussey

I updated the API to make sure abort_signal is never a naked parameter. Instead it is always part of an options object so others can be added later. Also set...

TODO: at least for `pipeline()`, I will create an `InterruptableStoppingCriteria` that will activate when the signal activates. I'll add it if no other stopping criteria, and convert any other to...

I have a version of transformers.js with abort signal handling at @sroussey/transformers [edit, both 3.3.3 and 3.4.0 versions]

You need more than fetch. You need fetch, ReadableStream, and cache after a quick glance. I think with those three you can hack together a global abort. Though if you...

No idea, but you can test my version by using `@sroussey/transformers` instead. [Differences in fork (README version)](https://github.com/sroussey/transformers.js/tree/v3-publish?tab=readme-ov-file#this-is-a-fork) [Differences in fork (code version)](https://github.com/huggingface/transformers.js/compare/main...sroussey:transformers.js:v3-publish)

@xenova If there is interest, I can rebase my work. @natanfudge and @jdp8 -- there is a way to abort generation since there is a break between words. There is...

I submitted a long time ago. And the use case is the same for me with model downloads. I have published a fork on npm you can try. Check the...

@jdp8 Forgot to @ you so you may have missed the above.

Correct. If I was just doing some server side stuff, aborting all would be fine. Likely I'd just terminate the process instead. Even in the browser, if you have transformers.js...

Maybe i am thinking of this all wrong, and I should be using a custom cache and prefilling it. Not sure i will get to it today, but I should...