Eric Dubé

I removed my change earlier because I broke the github action, so this has created a conflict - you can simply overwrite my change with what's in this PR

neat, apparently it lets me resolve the conflict myself

Looks like it got stuck. Is it expected that it got stuck where it did, or does that indicate a problem?

> Now, both amd64 and arm64 works. Would you accept that? Yes, that sounds good to me. For other architectures I think it's reasonable to consider this out-of-scope and expect...

This issue was incorrect - I needed to run `npm rebuild`. Apparently Puter works in node.js versions as low as `16`.

That makes sense, but why would more than 16KiB worth of files be emitted before a more previous file's stream has ended?

That almost sounds like what I was thinking, but the description of when to pause sounds different and I don't understand why that implies a chunk needs to be stored...

this should be fixed now

> Both self-hosted puter and puter.com dont work Can you elaborate on this? Did you encounter two corrupted files - one on each deployment?

> and used it on localhost too Thanks, that makes a lot more sense. You're running a relatively old version of this repo before the self-hosted backend was available, so...