Jean Boussier

> I'm curious -- is that the case even when not using M:N scheduling on the main ractor? What thread does it get called from? 🤔 Yes, it's fired from...

FYI @jpcamara

> As an alternative fix, we could investigate the `ON CONFLICT DO NOTHING` idea Yeah, sounds nice, can be an extra `supports_....` in the adapters.

So I'm positive on the feature, but not really a fan of the implementation. I think providing a single callback that receive the original exception and is free to raise...

> What do you think of this direction? That's pretty much what I had in mind yes.

I'll try to get some time to review this. But also there's a current effort by the foundation to work on guides, so this might interest them. cc @carlosantoniodasilva and...

> but it never gets run and the runtime is blocked waiting for its termination If the parent process is blocked on `wait`, it means the child process is still...

> What can be the reason? This test is about restarting the reaper thread in the child, which we do from an `after_fork` callback that is executed before everything else....

> Do you have an idea on why that can be and how to solve it? No, I'd need to dig into it. I barely had a look. > maybe...

The second one for sure.