Hi everyone, is it possible to run Dagster in debug mode and use breakpoints? I am using VSCode

same q for PyCharm

yes breakpoint debug works for me with vscode, since it's just regular python and pytest works for me out of the box

@Martin Picard so you can run Dagster and running a Job will trigger a breakpoint? Or do you mean that you Debug a specific Python file and it runs the default debugger?

ah sorry I misunderstood, in theory vscode can attach to any python process https://code.visualstudio.com/docs/python/debugging I was talking specifically about test debugging, which works great, would recommend debugging your unit tests or creating a test for your specific problem first

Thanks for the links 🙂 I was hoping to have something like developing and debugging Azure Functions locally which lets you run a function (which is basically a web app) locally and then you can use breakpoints which are triggered when different parts of the app are called. Unit testing and debugging will work too 🙂

code step through, running in debug mode, is a nice feature in pycharm too. idk how realisic it is to expect dagster to cater to this but it's nice.

I tried attaching to the process ID no success. Would be really nice for debugging though. Currently I just use logging only in my development process.

So, we can't attach a debugger to dagster running on localhost and debug in PyCharm, right? Was anybody able to do this?

my suspicion would be that it's possible, but I'm not super familiar with PyCharm or attaching debuggers to running Python processes

I tried attaching to the process but it didn't work.. could you give it a go on your end?

sorry but this isn't a setup that I have

If you have vs code can you try 😄 I was not able to get it to work.

Not working in PyCharm too..

hi - what we have got working, in PyCharm, is runniing an execution in process. eg. a file: local_debug.py containing the following code, then run this file in debug mode in pycharm, works great. It does mean you need a code snippet for every asset you want to debug though, -> maybe there is a more efficient way to do this, but for now we're just building up a long debug file with all the code snippets and just toggle code comment for the bit you want to debug.

os.environ["DAGSTER_DEPLOYMENT_NAME"] = <...>
deployment_name = os.getenv("DAGSTER_DEPLOYMENT_NAME", "local")
resource_defs = configured_resources_by_deployment(deployment_name)

if __name__ == "__main__":
    sources = [sourceA.to_source_asset(), *source_multi_asset.to_source_assets()]
    materialize(assets=[asset_to_debug] + sources,
                partition_key=MultiPartitionKey({"rep_date": "2022-12-01", "scenario_key": "scenA"}),
                resources=resource_defs)

Okay so yeah this is something I also ended up with. A giant local_code.py file. Haha..