Joachim Jablon

When the PR is ready, press the big "Ready for review" button 

I have to admit I have limited multiprocessing experience (it just happens to never have been on my radar). From what I know, [Pipes and Queues](https://docs.python.org/3/library/multiprocessing.html#exchanging-objects-between-processes) might be what Python...

I'm a bit wary of changing the model just like this. I wonder if we should maybe add options (we don't have to pick them all): - Legacy runner that...

> We can add it as an experimental feature Yes that was my point: I'm comfortable with adding it, I'm comfortable with it having better support over some features (such...

I think providing a wrapper function for tasks would be a way to provide a hook before and after, and if we propagate the exception, it can also discriminate between...

> One thing that bothers me a bit is that in both scenarios, the context was already created, and thereby a start_timestamp is already set Aha, you assume that the...

Sure! Though I'm not sure we need to change things in the CI (we can add the fact that the CI runs on the branch after we merge), but we...

> Don't we want to run CI against those PRs before they get merged? Unless I'm mistaken, CI runs on all PRs regardless of the target branch AND on main...

Here you are. There's a `v3` branch, and I've set up the same branch protection rules on `v3` as on `main`. CI will run on PRs that target `v3` (that...

Closed by #1272