Ray Zane

We've also been seeing this issue pop up intermittently in our end-to-end test suites, and only in CI environments. We managed to get a reliable reproduction, but I don't think...

At the very least, emitting a warning or error when this situation is detected would be helpful, since I had no reason to believe what I was doing was problematic.

Actually, it seems like `disableConsoleIntercept: true` might be a better solution to this problem.

The solution above works pretty well, but it's not aware of methods like `#total_count`, etc. Here's a compiler that makes the types a bit more accurate. It's based on the...

No need to apologize! All improvements come with some risk, and parallelizing make is a valuable improvement.

We're running on CircleCI, where this is a known issue, but here are a few issues: * https://circleci.canny.io/cloud-feature-requests/p/have-nproc-accurately-reporter-number-of-cpus-available-to-container * https://support.circleci.com/hc/en-us/articles/10653544013467-Docker-Executor-returning-Total-Host-CPU-Cores * https://travis-ci.community/t/nproc-reports-32-cores-on-arm64/5851 * https://github.com/nodejs/node/issues/28762 The issue stems from using Docker...

It's quite possible that my understanding of how CircleCI works behind the scenes doesn't match reality. On CircleCI, I do not control how the docker image is launched. However, I...