Skip to content

REPL-driven, multi-process-native debugger features #113

@goodboy

Description

@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 and asked all the cool peeps what they use. Well here's a list of interesting stuff:

popular Python remote debuggers

What I want:

  • write breakpoint() in actor code and tractor does the right thing and yields std stream control in FIFO order to whatever actor got their message to the parent first
  • first class support for pdbpp, it's just too good not to use
  • the ability to switch between multiple actors who have breakpoints in a sensible way much like gdb does with threads

Profiling and other possible tools and approaches

A WIP list of tooling/instrumentation that might add to and/or inspire ideas for the future!


REPL driven, would love to have, features

As always, lurkers feel free to pipe in with ideas 🏄‍♂️

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions