-
all the private repos that msft would want to mine are prolly here.. Bo
- Joined on
2023-08-13
goodboy commented on pull request goodboy/tractor#18
Python 3.13 supportYou'll find the bulk of the strict-eg-style "sidestepping" is just this for now..
goodboy opened issue goodboy/tractor#22
Drop strict_exception_groups=False` owhen trio` does
goodboy commented on pull request goodboy/tractor#18
Python 3.13 supportwoof, this should be removed since that subpkg won't land until #12 ?
goodboy commented on pull request goodboy/tractor#18
Python 3.13 supportThis test demonstrates a footgun i recently discovered debugging silent process tree cancellation in `modden`.
goodboy commented on pull request goodboy/tractor#18
Python 3.13 supportNot sure if this is the right choice, seems like it can't hurt since we consider `greenback` a `--dev` dep?
goodboy pushed to main at goodboy/tractor
-
-
c91373148a Comment-tag pause points in `asycnio_bp.py`
-
-
-
- Compare 67 commits »
goodboy merged pull request goodboy/tractor#2
Prevent `asyncio` from abandoning guest-runs, `.pause_from_sync()` support via `.to_asyncio`
goodboy commented on pull request goodboy/tractor#2
Preventasyncio from abandoning guest-runs, .pause_from_sync() support via .to_asyncio
This is a pretty important step forward for the debugger REPL tooling since now you can definitely get multi-actor safe pausing from infected-`asyncio` actors including crash handling B)
goodboy commented on pull request goodboy/tractor#2
Preventasyncio from abandoning guest-runs, .pause_from_sync() support via .to_asyncio
Much thanks to @oremanj (from GH) for this fn!
goodboy commented on pull request goodboy/tractor#2
Preventasyncio from abandoning guest-runs, .pause_from_sync() support via .to_asyncio
Same as mentioned above; appears to be the best/most-reliable hack for the moment..
goodboy commented on pull request goodboy/tractor#2
Preventasyncio from abandoning guest-runs, .pause_from_sync() support via .to_asyncio
This is one of the critical-yet-questionable changes; `asyncio.Task.cancel()` seems to never work reliably and can often cause full guest-run abandonment, so instead we take the approach of touching any internal `Future` first and hoping for the best (which seems to work in practise!).
goodboy commented on pull request goodboy/tractor#2
Preventasyncio from abandoning guest-runs, .pause_from_sync() support via .to_asyncio
Replicating the same outcome waiting API as `Context`.
goodboy commented on pull request goodboy/tractor#2
Preventasyncio from abandoning guest-runs, .pause_from_sync() support via .to_asyncio
For back-lookers (from the future) these new excs drove the improved error translation semantics throughout the cancel and exit handling machinery.
goodboy commented on pull request goodboy/tractor#2
Preventasyncio from abandoning guest-runs, .pause_from_sync() support via .to_asyncio
This is the main error-translation-semantics that changed, more or less being more pedantic about which side errored/cancelled/exited-gracefully and whether it was independent of the other side.
goodboy pushed to aio_abandons at goodboy/tractor
-
-
-
-
-
- Compare 67 commits »
goodboy commented on pull request goodboy/tractor#2
Preventasyncio from abandoning guest-runs, .pause_from_sync() support via .to_asyncio
I mean anyone wanting to *click approve* (since they already built a buncha sh#! on top of this ;) would allow us to conduct the (normal)formal protocol to all things "community" and "foss".. @g…
goodboy pushed to main at goodboy/tractor
-
-
-
-
-
- Compare 191 commits »
goodboy merged pull request goodboy/tractor#7
Rework low-level-runtime to enforce a `msgspec`-defined, SC-supervision-protocol for IPC `Context`s
goodboy commented on pull request goodboy/tractor#7
Rework low-level-runtime to enforce amsgspec-defined, SC-supervision-protocol for IPC Contexts
Well if @guille approves..
goodboy opened issue goodboy/tractor#21
Typed-IPC-msgspec follow up (from #19)