goodboy
goodboy
In `tractor` every actor is both a (potential) *client* and *server*. Concocting a "native" feeling "remote debugger" shouldn't be that bad (they thought naively..), right? I did a little digging...
As part of the journey in #129 I discovered that no-one seems to have solved the problem of getting the *fancy features* of a modern Python debugger working in remote...
With the introduction of our multi-process debugger system in #126 via `await tractor.breakpoint()`, we probably need to consider how a user can call the standard `breakpoint()` from sync code in...
This turned up in working the CI for #129. Turns out `pexpect` (and thus [sensibly `pytest`](https://github.com/pytest-dev/pytest/blob/master/src/_pytest/pytester.py#L1449)) [doesn't support `spawn()` on Windows](https://pexpect.readthedocs.io/en/stable/overview.html#pexpect-on-windows) so we have no way to know with the...
I've been running into this problem using the new debugger support from #129: - `ctrl-c` while already in debugger - `SIGINT` during a request for the tty lock in the...
After my (yet again) completely in vain attempts to get code review of #243, *the lurkers* were kind enough to chime in with all sorts of neat ideas for how...
As a follow up to the core work done for #53 in #219 (originally #209) and the sidekick debugger improvements in #220 this is the list of outstandings and *would...
Like it sounds, with more refinements to come! This is a POC and seems to do about what I'd like; would appreciate lurker feedback 😉 ping @mikenerone, original author of...
Ugh, i don't even know what to say about this - lost a day writing a (should take 20m) container supervisor-actor and got lost in figuring out somehow (at least...
Got `breakpoint()` working sanely from sync code recently (PR coming) and am realizing maybe we can just avoid any `await tractor.breakpoint()` stuff by doing a bit of sync blocking inside...