juj

Previously I have been able to test end user setup by leaving out installing the dev dependencies. But because bootstrap is mandatory, and after this PR it will install python...

> I designed this change specifically with your workflow in mind. Thanks, that is much appreciated. > With this system that risk has been removed. The emscripten compiler code itself...

> The idea is that the _test runner_ has a hard dependency on these dev packages I guess this is the part that I feel off about. Currently there does...

> Its seems like we already have hard dependency on `psutil` in test code in `test/browser_common.py`... how does your CI handle that one? Both pywin32 and psutil are production dependencies...

That sounds good, if you have the cycles to slice the PR.

It is unfortunately currently not possible to have a single Audio Worklet thread operate against two different WebAssembly Modules. The WebAssembly code in a Wasm Audio Worklet is compiled in...

This is definitely a bit tricky situation. Would using multiple AudioContexts resolve this as a workaround? Or does that run into other problems on its own.. If you might want...

The use case of proxying to Worker itself is sound, because just enabling multithreaded programs require nonstandard HTTP server configuration. So applications that are based on async message passing multiprocessing-style...

Hmm with further testing, it looks like the issue was not "just" `[].slice.call(arguments)`, but the fact that it was enclosed in a `() => {}` lambda function. I.e. happens with...

This flake seems to be Chrome-specific btw - the flake does not occur on Firefox. I wonder if there could be a Chrome bug or improvement possible?