Currently in our docs for open_signal_receiver, we have an example of catching SIGHUP and using it to reload the application configuration. While talking to @wgwz today re: python-trio/snekomatic#41, I discovered that this example is maybe not so great, because readers who aren't already steeped in Unix tr

Current implementation of AsyncManualResetEvent event contains cancellable WaitAsync() while wiki says it is not implemented due to design reasons.
P.S.:
By the way, Great Thank you for this library.

The build section should talk about contrib. The contributing section should cover:

1. Differences between npm version and github version.
2. Process for building (or should that be in build) and running tests.
3. Contribution guidelines.

Just highlighting this in case you're interested, I took a fork of @dennisfabri racetimes example and extended it to run with Azure Functions and then extended again to publish to Azure EventGrid as a new extension inspired by the RabbitMQ example. Might be of interest to others.

https://github.com/craignicol/Eventflow.Example.Racetimes/tree/feature/event-grid-as-extension

Please, could you provide detailed installation instructions and a complete list of all dependencies, including their versions?

Preferably in the form of a tutorial providing all steps, how to install starhackit on a particular vagrant box, e.g. on most recent Ubuntu.
I.e.:

• Install VirtualBox (version [VirtualBoxVersion] or higher) and [Vagrant](https://www.vagrantup.com/docs/getting-starte

bug in README.md when_all_ready() example:

task<> example2()
{
...
// Unpack and handle each result individually once they're all complete.
for (int i = 0; i < 1000; ++i)
{
try
{
>>> std::string& record = tasks[i].result();
should be
std::string& record = resultTasks[i].result();
...
}

The video course links to the v2 branch of the repo and you mention bit.ly/fem-ts which also takes me there. Later you mention that the reduceDict solution will be in the repo. I found it in the v2-fem branch. That could be a potential source of confusion.

Context

It'd be helpful to describe possible migrations paths.

One idea:

const express = require('express')
const Huncwot = require('huncwot')

const app1 = express()
const app2 = new Huncwot()

app1.get('/', () => /* proxy to app2 here */)
app2.get('/', () => 'foo')

app1.listen(3333)
app2.listen(3334)

Not ideal for performance for sure, but it should make it