Official service-mngr to `tractor.hilevel` move

Such that we maintain that subsys in the actor-runtime repo (with hopefully an extensive test suite XD). Port deats, - rewrite `open_service_mngr()` as a thin wrapper that delegates into the new `tractor.hilevel.open_service_mngr()` but with maintenance of the `Services` class-singleton for now. - port `.service._daemon` usage to the new `ServiceMngr.start_service_ctx()` a rename from `.start_service_task()` which is now likely destined for the soon supported `tractor.trionics.TaskMngr` nursery extension. - ref the new `ServiceMngr.an: ActorNursery` instance var name. Other, - always enable the `tractor.pause_from_sync()` support via `greenback` whenever `debug_mode` is set at `pikerd` init.
Updated tractor method name.
2025-02-11 18:38:11 -05:00 · 2025-02-11 18:38:11 -05:00 · 2025-02-11 18:38:11 -05:00 · 2025-02-11 18:38:11 -05:00
2 changed files with 7 additions and 11 deletions
--- a/piker/brokers/binance/api.py
+++ b/piker/brokers/binance/api.py
@ -567,7 +567,6 @@ class Client:
    ) -> str:
        return {
            'USDTM': 'usdtm_futes',
-            'SPOT': 'spot',
            # 'COINM': 'coin_futes',
            # ^-TODO-^ bc someone might want it..?
        }[pair.venue]
--- a/piker/tsp/init.py
+++ b/piker/tsp/init.py
@ -458,15 +458,13 @@ async def start_backfill(
                    'bf_until <- last_start_dt:\n'
                    f'{backfill_until_dt} <- {last_start_dt}\n'
                )
-                # UGH: what's a better way?
-                # TODO: backends are responsible for being correct on
-                # this right!?
-                # -[ ] in the `ib` case we could maybe offer some way
-                #     to halt the request loop until the condition is
-                #     resolved or should the backend be entirely in
-                #     charge of solving such faults? yes, right?
-                # if timeframe > 1:
-                #     await tractor.pause()
+
+                # ugh, what's a better way?
+                # TODO: fwiw, we probably want a way to signal a throttle
+                # condition (eg. with ib) so that we can halt the
+                # request loop until the condition is resolved?
+                if timeframe > 1:
+                    await tractor.pause()
                return

            assert (
@ -580,7 +578,6 @@ async def start_backfill(
                    'crypto',
                    'crypto_currency',
                    'fiat',  # a "forex pair"
-                    'perpetual_future',  # stupid "perps" from cex land
                }:
                    # for now, our table key schema is not including
                    # the dst[/src] source asset token.
Author	SHA1	Message	Date
Tyler Goodlet	cd4fd02e5c	Official service-mngr to `tractor.hilevel` move Such that we maintain that subsys in the actor-runtime repo (with hopefully an extensive test suite XD). Port deats, - rewrite `open_service_mngr()` as a thin wrapper that delegates into the new `tractor.hilevel.open_service_mngr()` but with maintenance of the `Services` class-singleton for now. - port `.service._daemon` usage to the new `ServiceMngr.start_service_ctx()` a rename from `.start_service_task()` which is now likely destined for the soon supported `tractor.trionics.TaskMngr` nursery extension. - ref the new `ServiceMngr.an: ActorNursery` instance var name. Other, - always enable the `tractor.pause_from_sync()` support via `greenback` whenever `debug_mode` is set at `pikerd` init.	2025-02-11 18:38:11 -05:00
Nelson Torres	eb229f3522	Updated tractor method name.	2025-02-11 18:38:11 -05:00
Tyler Goodlet	4d29722794	More service-mngr clarity notes Nothing changing functionally here just adding more `tractor` operational notes, tips for debug tooling and typing fixes B) Of particular note is adding further details about the reason we do not need to call `Context.cancel()` inside the `finally:` block of `.open_context_in_task()` thanks to `tractor`'s new and improved inter-actor cancellation semantics Bo	2025-02-11 18:38:11 -05:00
Tyler Goodlet	77703f2201	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!	2025-02-11 18:38:11 -05:00