goodboy
goodboy
Heh it's definitely blowing up CI [looks like3 tests](https://github.com/goodboy/tractor/runs/4693814294?check_suite_focus=true); so we might need a slightly different approach or to fix those tests. Having a test in the suite would be...
@didimelli sweet! Yeah just to clarify the issue, basically it's summarized as follows: - `ActorNursery.run_in_actor()` is syntactic sugar around `.start_actor()` where the portal is requested to implicitly run a single...
@houtenjack thanks for the input! Yes, cancellation will also work **but** (and this is important) we also want to make sure we aren't limiting the ability of users to eventually...
Another question is whether a child actor which is cancelled due to an error from a *sibling* in the nursery group (in this case `not_raising`) should also raise a `trio.Cancelled`...
> Let's see if I understand the issue: 💯. Only things I might emphasize is that `task A` is a *remote task* from the perspective of the nursery **and**, >the...
Heh, so despite trying all the things the test suite is still be grumpy and it's making me wonder if we should just redo the entire `.run_in_actor()` API in the...
Yeah, after spelunking the original design a bit yesterday I *think* I'm of the opinion that we should *at the least* decouple `.run_in_actor()` from the nursery internals and *at most*...
Added a couple more patches to #288 to attempt to make the test suite happy (in terms of errors we previously expected in a `MultiError`) but as mentioned I wonder...
> I think that since this project is heavily inspired by trio, many people will approach tractor the same way I did, and so they will reach for a trio-like...
> I am not particularly interested in `.run_in_actor()` calls specifically. Yeah, if there's one thing I've discovered since adding `.open_context()` it's that everything can be built from that set of...