Comparing 5cdb2ca68a..a42ba3a862 - tractor - Pikers Dev

..

Author	SHA1	Message	Date
Tyler Goodlet	a42ba3a862	Hide `._rpc._invoke()` frame, again..	2025-09-05 15:10:38 -04:00
Tyler Goodlet	710e4fc1d7	Explain the `infect_asyncio: bool` param to pass in RTE msg	2025-09-05 15:10:38 -04:00
Tyler Goodlet	6263480b3e	Toss in masked `.set_trace()` for unshielded `.pause()` debug	2025-09-05 15:10:38 -04:00
Tyler Goodlet	0a4cdac345	Mask tpt-closed handling of `chan.send(return_msg)` A partial revert of commit `c05d08e426` since it seem we already suppress tpt-closed errors lower down in `.ipc.Channel.send()`; given that i'm pretty sure this new handler code should basically never run? Left in a todo to remove the masked content once i'm done more thoroughly testing under `piker`.	2025-09-05 15:10:38 -04:00
Tyler Goodlet	9a5b82e2cd	More `TransportClosed`-handling around IPC-IO For IPC-disconnects-during-teardown edge cases, augment some `._rpc` machinery, - in `._invoke()` around the `await chan.send(return_msg)` where we suppress if the underlying `Channel` already disconnected. - add a disjoint handler in `_errors_relayed_via_ipc()` which just reports-n-reraises the exc (same as prior behaviour). * originally i thought it needed to be handled specially (to avoid being crash handled) but turns out that isn't necessary? * hence the also-added-bu-masked-out `debug_filter` / guard expression around the `await debug._maybe_enter_pm()` line. - show the `._invoke()` frame for the moment.	2025-09-05 15:10:38 -04:00
Tyler Goodlet	369fca6cc1	Use new `pkg_name` in log-sys test suites	2025-09-05 15:08:09 -04:00
Tyler Goodlet	3af55d9d64	Implicitly name sub-logs by caller's mod That is when no `name` is passed to `get_logger()`, try to introspect the caller's `module.__name__` and use it to infer/get the "namespace path" to that module the same as if using `name=__name__` as in the most common usage. Further, change the `_root_name` to be `pkg_name: str`, a public and more obvious param name, and deprecate the former. This obviously adds the necessary impl to make the new `test_sys_log::test_implicit_mod_name_applied_for_child` test pass. Impl detalles for `get_logger()`, - add `pkg_name` and deprecate `_root_name`, include failover logic and a warning. - implement calling module introspection using `inspect.stack()/getmodule()` to get both the `.__name__` and `.__package__` info alongside adjusted logic to set the `name` when not provided but only when a new `mk_sublog: bool` is set. - tweak the `name` processing for implicitly set case, - rename `sub_name` -> `pkg_path: str` which is the path to the calling module minus that module's name component. - only partition `name` if `pkg_name` is `in` it. - use the `_root_log` for `pkg_name` duplication warnings. Other/related, - add types to various public mod vars missing them. - rename `.log.log` -> `.log._root_log`.	2025-09-05 15:08:09 -04:00
Tyler Goodlet	093ad02beb	Add an implicit-pkg-path-as-logger-name test A bit of test driven dev to anticipate support of `.log.get_logger()` usage such that it can be called from arbitrary sub-modules, themselves embedded in arbitrary sub-pkgs, of some project; the when not provided, the `sub_name` passed to the `Logger.getChild(<sub_name>)` will be set as the sub-pkg path "down to" the calling module. IOW if you call something like, `log = tractor.log.get_logger(pkg_name='mypylib')` from some `submod.py` in a project-dir that looks like, mypylib/ mod.py subpkg/ submod.py <- calling module the `log: StackLevelAdapter` child-`Logger` instance will have a `.name: str = 'mypylib.subpkg'`, discluding the `submod` part since this already rendered as the `{filename}` header in `log.LOG_FORMAT`. Previously similar behaviour would be obtained by passing `get_logger(name=__name__)` in the calling module and so much so it motivated me to make this the default, presuming we can introspect for the info. Impl deats, - duplicated a `load_module_from_path()` from `modden` to load the `testdir` rendered py project dir from its path. \|_should prolly factor it down to this lib anyway bc we're going to need it for hot code reload? (well that and `watchfiles` Bp) - in each of `mod.py` and `submod.py` render the `get_logger()` code sin `name`, expecting the (coming shortly) implicit introspection feat to do this. - do `.name` and `.parent` checks against expected sub-logger values from `StackLevelAdapter.logger.getChildren()`.	2025-09-05 15:08:09 -04:00
Tyler Goodlet	b4bacbc766	Start a logging-sys unit-test module To start ensuring that when `name=__name__` is passed we try to de-duplicate the `_root_name` and any `leaf_mod: str` since it's already included in the headers as `{filename}`. Deats, - heavily document the de-duplication `str.partition()`s in `.log.get_logger()` and provide the end fix by changing the predicate, `if rname == 'tractor':` -> `if rname == _root_name`. * also toss in some warnings for when we still detect duplicates. - add todo comments around logging "filters" (vs. our "adapter"). - create the new `test_log_sys.test_root_pkg_not_duplicated()` which runs green with the fixes from ^. - add a ton of test-suite todos both for existing and anticipated logging sys feats in the new mod.	2025-09-05 15:08:09 -04:00
Tyler Goodlet	e9f3689191	Add "ignore-case-handling" to exc unmasker Since it turns out there's even case(s) in `trio` core that are guilty (of implementing things like checkpoints in exc handlers), this adds facility for ignoring explicit cases via `inspect.FrameInfo` field matching from the unmasked `exc_ctx` within `maybe_raise_from_masking_exc()`. Impl deats, - use `inspect.getinnerframes()/getmodule()` to extract the equivalent "guilty place in code" which raised the masked error which we'd like to ignore and not unmask. - start a `_mask_cases: dict` which describes the entries to ignore by matching against a specific `FrameInfo`'s fields from indexed from `getinnerframes()`. - describe in that table the case i hit with `trio.WouldBlock` being always masked by a `Cancelled` due to way `trio.Lock.acquire()` implements the blocking case in the would-block handler.. - always call into a new `is_expected_masking_case()` predicate (from `maybe_raise_from_masking_exc()`) on matching `exc_ctx` types.	2025-09-05 14:54:54 -04:00
Tyler Goodlet	93aa39db07	Always pop `._Cache.resources` AFTER `mng.__aexit__()` The correct ordering is to de-alloc the surrounding `service_n` + `trio.Event` after the `mng` teardown ensuring the `mng.__aexit__()` never can hit a ref-error if it touches either (like if a `tn` is passed to `maybe_open_context()`!	2025-09-05 14:54:41 -04:00

Diff Content Not Available