Hood Chatham

With my commit: ```sh Invoking CMake setup: 'cmake /src/packages/dlib/build/dlib-19.22.1/tools/python -DCMAKE_LIBRARY_OUTPUT_DIRECTORY=/src/packages/dlib/build/dlib-19.22.1/build/lib.linux-x86_64-3.9 -DPYTHON_EXECUTABLE=/usr/local/bin/python3.9 -DCMAKE_CXX_FLAGS=-std=gnu++11 -DCMAKE_CXX_COMPILE_FEATURES=cxx_constexpr -DCMAKE_BUILD_TYPE=Release' ``` Before: ```sh Invoking CMake setup: 'cmake /src/packages/dlib/build/dlib-19.22.1/tools/python -DCMAKE_LIBRARY_OUTPUT_DIRECTORY=/src/packages/dlib/build/dlib-19.22.1/build/lib.linux-x86_64-3.9 -DPYTHON_EXECUTABLE=/usr/local/bin/python3.9 -DCMAKE_BUILD_TYPE=Release' ``` So it did add...

Looks like memory corruption in xgboost and opencv @ryanking13...

> the error message is `indirect call signature mismatch` I think the bad call is because of earlier memory corruption. In wasm there is no memory protection, you can dereference...

Since these are both new packages, maybe we should disable them too until we figure out how to make them work with the newer Emscripten? I think it's important to...

Sounds good.

My guess is that it will still break the two packages. But we may be planning to start only updating Python and Emscripten at the same time once a year...

> error-stack-parser does not export StackFrame from ErrorStackParser in version 2.0.7 which is currently installed with pyodide. It has been fixed in 2.1.0 so I'm assuming that updating version will...

Seems like the new version still doesn't work but there's a different error.

I've periodically looked into this but I have no idea how to fix it...

It's been an ongoing issue for us that we don't have any developers with much JavaScript/webpack expertise.