How do you get the logs when the debugger isn't attaching

[elmehalawi]

I'm trying to connect the debugger to my django application. I added this to the manage.py file:

    if settings.DEBUG:
        if os.environ.get('RUN_MAIN') or os.environ.get('WERKZEUG_RUN_MAIN'):
            import ptvsd
            ptvsd.enable_attach(address=('0.0.0.0', 7000), redirect_output=True)

And I have the following launch configuration:

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python backend",
            "type": "python",
            "request": "attach",
            "pathMappings": [
                {
                    "localRoot": "${workspaceFolder}/backend",
                    "remoteRoot": "/app"
                }
            ],
            "port": 7000,
            "host": "127.0.0.1"
        }
    ]
}

This setup used to work, and as far as I can tell, I haven't changed anything recently. But it stopped working the other day. Maybe there was an update that introduced a breaking change, I don't know.

Now what happens when I run this launch config is the debug controls show up for a few seconds then disappear. I don't get any other indication of what's happening.

Is there a way to get logs so I can see what's going on? I tried getting the vscode logs like this :

cd Library/Application\ Support/Code/logs/SOMELONGNUMBER
tail -f main.log

And I got an output that looks like this:

[2021-03-29 02:02:18.976] [main] [info] update#setState idle
[2021-03-29 02:02:48.978] [main] [info] update#setState checking for updates
[2021-03-29 02:02:49.368] [main] [info] update#setState idle
[2021-03-29 10:34:12.613] [main] [info] update#setState checking for updates
[2021-03-29 10:34:13.168] [main] [info] update#setState idle
[2021-03-29 11:44:31.188] [main] [info] update#setState checking for updates
[2021-03-29 11:44:31.624] [main] [info] update#setState idle

But nothing when I try to run the debugger.

[brettcannon]

If there were any logs it would be in the Output Panel.

But can I ask where you got the instructions for debugging? We have not used ptvsd as our debugger in quite some time; debugpy is our debugger. Please see https://code.visualstudio.com/docs/python/debugging for instructions on how to set up debugging. And we have support for Django in-the-box, so you shouldn't have to connect remotely to it if you're running your dev server locally.

[elmehalawi]

Hey thanks for the reply. I'm running django inside a docker container using docker-compose. That's why I'm using attach. But the django support you mentioned looks really interesting. I can see from the django tutorial that it's really easy to set up on the local machine. I'll try to adapt this to my docker setup somehow.

[elmehalawi]

@brettcannon so I've been looking around, and I can't seem to figure it out. Is my use case supported?

Can I debug a django app running in a docker container by attaching it? Or do I have to modify my setup to run the python server separately when I start my project?

This is the only guide I found that attaches to the django project, and yeah it uses ptvsd. Maybe that's what broke because it's outdated?

[brettcannon]

Are you using the Remote - Containers extension? If you are then you can debug like it's local on your machine and avoid having to do a remote connection (IOW if you're not I highly recommend giving it a try 😄 ). Otherwise our remote debugging instructions cover how to do this (and yes, anything suggesting you use ptvsd is outdated).

[elmehalawi]

In case this helps anyone, I added the debug config to manage.py by putting this inside if __name__ == "__main__":

    if settings.DEBUG:
        if os.environ.get("RUN_MAIN") or os.environ.get("WERKZEUG_RUN_MAIN"):
            import debugpy

            debugpy.listen(("0.0.0.0", 5678))

And the regular attach launch config worked.