Joyee Cheung

> we need to another a new API that allows to synchronously wait for another spawned thread. It seems you are describing [`Atomics.wait()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Atomics/wait), which is what the current `module.register()` implementation...

Unless there is a standardized API for doing this, I think in general it's best to let the user land be creative when developing a helper that doesn't have to...

Having something on npm SGTM if someone is up for designing an API and implementing it (at this point I would be surprised if there aren’t already some existing helpers...

> What are the possible performance issues with manual Atomic.wait? Or does it just do that under the hood already? `module.register()` (off-thread) already does `Atomic.wait()` (for `require()` customization in imported...

Oh wait, I think the container builds are already incremental. Though it might still help when we have to restart the containers. I remember there used to be outages when...

just noticed that `brew cleanup` might be useful too, I ran it as administrator and it cleaned up ~500MB for https://github.com/nodejs/jenkins-alerts/issues/526

Some other finds: 1. `/Users/iojs//jenkins_err.log` can take up hundreds of megabyes. It should be safe to clean it up? 2. `/Users/iojs/Library/Caches/node-gyp/` can build up to gigabytes. I think this is...

I think a PR adding it to the repo would be useful. We could also have some more eyeballs in the review to make sure we are not deleting things...

The summit has passed. closing.

The summit has passed. closing.