(if it matters, in my case dagit is not local, at least for the interesting debugs that I am looking for)

so these tools were designed for capturing a run as you see it in your dagit to send to someone (ie the dagster team) who doesn’t have access to your dagit server. They can take the file and load it in a tool like

dagit-debug

to see what you see in your dagit instance

one thing to note is there is

context.pdb

on the

OpExecutionContext

if you are trying to run and debug stuff locally

I was thinking that it would contain the "instantiated" resources/configs for a job (how this would work with secrets would be tbd I guess) so that it would actually run in an environment with all the right packages installed and could be debugged in a debugger to repo the issue

as opposed to (at least what I do now) creating a test where I recreate the resources/config manually, and then run/debug it that way