WIP: Replace ptvsd with debugpy to match modern VS Code

[justinclift]

What type of PR is this?

• Other

Description

VS Code has moved to using debugpy for debugging rather than the old (archived) ptvsd.

This (very simple) PR updates our code to use debugpy now too.

NOTE - This PR is a work in progress. 😄

How is this tested?

• Unit tests (pytest, jest)
• E2E Tests (Cypress)
• Manually
• N/A

Related Tickets & Documents

Useful reference info: https://github.com/microsoft/debugpy/wiki/Switching-over-from-%60ptvsd%60-to-%60debugpy%60

Redash documentation that will need updating: https://redash.io/help/open-source/dev-guide/debugging/ (source)

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

[justinclift]

@gaecoli @wlach @eradman @lucydodo How are you doing interactive debugging of Redash these days?

I'm trying this debugpy approach on macOS with Visual Studio Code, and it seems to be working ok for the server process.

Haven't tried it for debugging a worker process yet though. My suspicion is we'll need to add some extra code for that, though I'm not 100% sure.

My initial thought for that is perhaps something like this in an appropriate class (TBD) in something common to all the workers:

if os.environ.get("REMOTE_DEBUG_WORKER"):
    import debugpy

    debugpy.listen(("0.0.0.0", 5679))
    debugpy.wait_for_client()

Note the different port (5679) there than the debug port used for the server (5678). I'm also not sure if we should do it that way - which would potentially enabling debugging both server and worker at the same time - or if we'd want to force just debugging a single thing at a time.

Thoughts?

[eradman]

I have not used remote Python debugging, so I'll defer to others on this.

[justinclift]

No worries Eric. What's the approach you're using for debugging? Starting the individual processes locally then?

[gaecoli]

I have not used remote Python debugging, so I'll defer to others on this.

me toooooo.