goodboy
goodboy
Extremely interested in the idea of supporting direct spawn of async `rust` tasks (maybe in a diff thread) in our actor tree and **even further** eventually having a rust-native nursery...
After having seen this style in `anyio`'s latest release: https://github.com/agronholm/anyio/pull/599/files#diff-1fb03ea452beca16c76e364dc7f8ffe3dfcbb20be7e732cc5a552cba32fd771aR104 which it turns out, `trio` **also already supports this** :boom: (well via `trio_typing`), https://github.com/python-trio/trio/blob/348713a7ae73c1afaef79969c90c57e12f4f098b/trio/_channel.py#L93 ANNDDD apparently since it's being proposed...
### First draft justifications and theoretical underpinning The main focus of this effort is to provide a simple and low(er) level API for the management of shared memory array/buffers for...
As per some discussion in the `trio` gitter and starting something toward #22 and supporting our debugger crash mode from within a `trio`-compat task nursery. --- ### Idea: a `trio.Nursery`...
`trio` changed it's subprocess API as per the large discussion in https://github.com/python-trio/trio/issues/1104. Summary: - they dropped the `Process.aclose()` behaviour due to it being "surprising", prone to bugs and, > Process.aclose...
This has been on the idea backlog for a long while, obviously in pursuit of something like what's in `erlang's OTP` and consequently `elixer`: - https://blog.stenmans.org/theBeamBook/#CH-Calls - https://blog.appsignal.com/2021/07/27/a-guide-to-hot-code-reloading-in-elixir.html --- ####...
Per https://github.com/python-trio/trio/issues/2135#issuecomment-934109228 and #359 it'd be kinda interesting to try out a couple things: - the possibility of *embedding* our runtime in a `@ray.remote` thread - further, adding support to...
This is an idea that just popped up randomly when looking through some `ray` examples / discussion, particularly this `trio` issue comment: https://github.com/python-trio/trio/issues/2135#issuecomment-934109228 ```python import ray ray.init() @ray.remote def task():...
As found in d6ed97d0 of the #351 work, there is a nasty issue that causes an un-interrupt-able hang when we use enough `tractor.breakpoint()`s in the right spots *and* infected `asyncio`...
As a breakout from #136, I'm dumping some recent research links around the possibility of supporting `QUIC` as being our desired transport in the longer run instead of `TCP` :surfer:...