piker/piker/service
Tyler Goodlet de6189da4d Drop `.cancel_actor()` from `maybe_spawn_daemon()`
Since `tractor`'s new and improved inter-actor cancellation semantics
are much more pedantic, AND bc we use the `ServiceMngr` for spawning
service actors on-demand, the caller of `maybe_spawn_daemon()` should
NEVER conduct a so called "out of band" `Actor`-runtime cancel request
since this is precisely the job of our `ServiceMngr` XD

Add a super in depth note explaining the underlying issue and adding
a todo list of how we should prolly augment `tractor` to make such cases
easier to grok and fix in the future!
2024-08-21 17:37:40 +00:00
..
__init__.py Prep service mngr for move to `tractor.hilevel` 2024-08-20 23:01:51 -03:00
_actor_runtime.py Prep service mngr for move to `tractor.hilevel` 2024-08-20 23:01:51 -03:00
_ahab.py Prep service mngr for move to `tractor.hilevel` 2024-08-20 23:01:51 -03:00
_daemon.py Drop `.cancel_actor()` from `maybe_spawn_daemon()` 2024-08-21 17:37:40 +00:00
_mngr.py Prep service mngr for move to `tractor.hilevel` 2024-08-20 23:01:51 -03:00
_registry.py Ignore `ContextCancelled`s from non-mngr requests 2024-01-04 10:06:42 -05:00
_util.py Use a single log for entire `.service` subsys 2023-05-09 14:49:26 -04:00
elastic.py Prep service mngr for move to `tractor.hilevel` 2024-08-20 23:01:51 -03:00
marketstore.py Prep service mngr for move to `tractor.hilevel` 2024-08-20 23:01:51 -03:00