Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Debugger hits breakpoints, but doesn't retrieve variables or continue execution

Open
#1,497 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker, docker-compose, python, vscode
Domain
devtools

Research direction

Reproduce the Flask attach setup using debugpy.listen(("0.0.0.0", 5678)) and the supplied launch.json, with the Docker and Docker Compose port mapping. Start by reviewing the linked adapter, pydevd, and server logs; done means breakpoints expose variables and execution can continue.

Written by the indexing model from the issue text.

Description

bug

Environment data

  • debugpy version: 1.8.0
  • OS and version: OSX 14.2.1 (ARM / Apple Silicon M2)
  • Python version: 3.8.18
  • Using VS Code or Visual Studio: VS Code 1.85.1

Actual behavior

Screen recording because it's clear: https://youtu.be/kKX6Oi2mu14

Description:

  • I'm launching with: debugpy.listen(("0.0.0.0", 5678))
  • My setup is a docker & docker compose file, deployed via Orbstack, which exposes & maps port 5678
  • I'm running a Flask app.
  • My launch.json is here:
    { "name": "Backend attach (Docker)", "type": "python", "request": "attach", "justMyCode": false, "connect": { "host": "0.0.0.0", // replace this with remote machine name "port": 5678 }, "pathMappings": [ { "localRoot": "${workspaceFolder}", "remoteRoot": "/app" } ] }

Here are the log files:
debugpy.adapter-56.log
debugpy.adapter-104.log
debugpy.pydevd.14.log
debugpy.pydevd.62.log
debugpy.server-14.log
debugpy.server-62.log

Expected behavior

I expect to see variables and continue execution.

Dominant language
Python
Stars
2.5k
Forks
202
Avg merge
5d 1h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/debugpy

All issues in microsoft/debugpy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.