Darren Worrall

The ability to specify the path to the ansible executable should be enough, you could pick the script installed in the virtualenv.

@wuub did you make any progress with your new receiver? I have an RX-A6A myself and have been walking a path of issues leading me here 😅 Similar sorts of...

I saw that integration and initially disregarded it because it didn't think it could control the source input of the receiver, but I dug deeper and found that it can,...

> If you mean Linux then I'm not sure if GitHub Actions supports that, but maybe there has been an update I missed? There are [arm runners in private beta](https://resources.github.com/devops/accelerate-your-cicd-with-arm-and-gpu-runners-in-github-actions/),...

I did also try building the tip of main a few weeks ago and got an actual [build error](https://github.com/DazWorrall/binaryen/actions/runs/7756223176/job/21153113813#step:9:237) fwiw, 116 built but failed the tests. Let me refresh my...

Ok, tip of main still failing to build: https://github.com/DazWorrall/binaryen/actions/runs/7979012200/job/21785404126#step:9:240 > `/src/src/support/small_vector.h:32:38: error: '.wasm::SmallVector::fixed' may be used uninitialized [-Werror=maybe-uninitialized]` Build is ok on x86_64 (or at least, the x86_64 version of...

The gcc version in both the aarch64 and x86_64 container is 13.2.1, and the x86_64 build works 🤷 Running `ninja -v install`, if I'm reading the logs right, there is...

Ok, I grabbed some native hardware for this (a ~90 minute emulated build time would have taken quite a while to bisect!): 141f7cad3aa516db3828e619b31fe681e46a151b (https://github.com/WebAssembly/binaryen/pull/6212) is the first commit which fails...

I should add that the build above was ran in the same docker container used in CI (`node:lts-alpine`) for consistency, but I was also able to replicate on debian bullseye...

If you're happy with that I will try to do so conservatively.