tractor/tractor/devx
Tyler Goodlet f5056cdd02 Mk `test_crash_handler_cms` suite go green
Turns out there were some subtle internal bugs discovered by the just
added `tests/devx/test_tooling::test_crash_handler_cms` suite.

So this fixes,

- a mis-ordering around `rt_repl_fixture :=` in the logic of
  `DebugStatus.maybe_enter_repl_fixture()`.

- `.devx.debug._post_mortem._post_mortem()` ensuring we now **always**
  call `DebugStatus.release()`, and thus unwind the exist-stack managing
  the `repl_fixture` exit/teardown, **even in the case** where
  `yield False` is delivered from the user-fixture-fn (meaning
  `dnter_repl=False`) thus triggering an early `return` (as is done in
  the new test suite).
2025-07-14 18:07:50 -04:00
..
debug Mk `test_crash_handler_cms` suite go green 2025-07-14 18:07:50 -04:00
__init__.py Mk `.devx._debug` a sub-pkg `.devx.debug` 2025-07-14 00:00:12 -04:00
_frame_stack.py Mv `.hide_runtime_frames()` -> `.devx._frame_stack` 2025-07-14 00:00:12 -04:00
_stackscope.py Report `enable_stack_on_sig` on `stackscope` import failure 2025-07-14 13:15:07 -04:00
cli.py Mk debugger tests work for arbitrary pre-REPL format 2025-03-20 15:07:27 -04:00
pformat.py Mv in `modden.repr` content: some `reprlib`-utils 2025-07-13 23:33:47 -04:00