goodboy
goodboy
There's [a section](https://github.com/tgoodlet/tractor/tree/contexts#actor-local-variables) on how this works right now but I'd really like to move to the way `trio` does it. Namely, - create per-actor [`contextvars`](https://docs.python.org/3.7/library/contextvars.html) like variables similar to...
[As mentioned](https://github.com/goodboy/tractor/pull/176#issuecomment-762418385) in #176 we could probably add a nicer way to manually submit "work jobs" to our "worker pool" example thing. I've got some thoughts about a full-duplex streaming...
Though I'm pretty much entirely against apis of this sort: 1. because they're imo entirely superfluous and use classes unnecessarily, and 2. because they're enforcing behind-the-scenes object setup and persistence...
Once #181 lands and all dependent projects are ported, we can safely move to the new `trio.run()` based entry api. The ideal user facing API instead looks like: ```python import...
@parity3 made a gitter request for a system to delegate work to an actor/task cluster or *pool*. >for my use case, I've got multiple "clients" that wish to use the...
#129 [adds a private `ExitStack`](https://github.com/goodboy/tractor/pull/129/files#diff-772a4e6cbad97300b849394751b56c7e967003d4cdf23ac6acad6e557d797e95R179) to `Actor` for the purposes of running some teardown when the runtime completes. It's used inside `piker`'s new shared memory FSP system for tearing down...
The new [sync sleep test](https://github.com/goodboy/tractor/pull/129/files#diff-dee4530dcdbd3fbcbcb61142a5fb22fa1c35c92014b5239e6b3562b4c0b46307R429) added in #126 seems to hang on windows? Not sure what's up here; needs a manual test from a collaborator.
This is a question about our public iter-actor task spawning api. Currently there are 2 methods which allow invoking tasks in remote actors: - [`ActorNursery.run_in_actor()`](https://github.com/goodboy/tractor/blob/master/tractor/_trionics.py#L89) - [`Portal.run()`](https://github.com/goodboy/tractor/blob/master/tractor/_portal.py#L180) Though these look...
I've been in talks with @guilledk surrounding this and it looks like we may do some work with building out some `pytest`-`docker` type plugin stuff to get it all running...
Just dumping some links: - https://github.com/dwoz/python-nat-hole-punching