Autocomplete does not work in debug console of the first debugging session

[serend1p1ty]

Environment data

• VS Code version: 1.40.2
• Extension version (available under the Extensions sidebar): 2019.11.50794
• OS and version: win10
• Python version (& distribution if applicable, e.g. Anaconda): Latest
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
• Relevant/affected Python packages and their versions: None
• Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info How to update the language server to the latest stable version vscode-python#3977): Jedi

Expected behaviour

When I start the first debugging session after launch vscode, autocomplete does not work in debug console.
But the strange problem won't appear in the second debugging session.

Actual behaviour

Autocomplete can work in the first debugging session.

Logs

> ~/anaconda3/envs/person_search/bin/python completion.py
cwd: ~/.vscode-server/extensions/ms-python.python-2019.11.50794/pythonFiles
> ~/anaconda3/envs/person_search/bin/python completion.py
cwd: ~/.vscode-server/extensions/ms-python.python-2019.11.50794/pythonFiles

[kimadeline]

Hi @520Chris 👋 Thank you for reaching out. I could reproduce the bug, and I can confirm that it's a regression in the extension:

• can reproduce with 2019.11.50794, but not with 2019.10.44104
• can reproduce the bug with:
  • a conda environment
  • a Python interpreter set by pyenv
• cannot reproduce the bug with:
  • a system install of Python
  • a virtual environment

[serend1p1ty]

Thank you very much. looking forward to a fix.

[serend1p1ty]

Is there any progress?

[brettcannon]

@520Chris unfortunately we don't give out updates on work.

[serend1p1ty]

I know, thanks for your response.

[OmeGak]

Not sure why this issue was closed. I'm experiencing this behavior consistently myself on a virtualenv.

[serend1p1ty]

Because this problem has not been fixed for nearly a year, I have lost patience and no longer pay attention to the latest progress.

[OmeGak]

Would you mind reopening it? An open issue is useful for maintainers and community to keep track of still existing problems.

[ewerybody]

I'm just having this issue again. And for some reason it keeps persisting now. I already used to develop a habit of restarting debug mode when I start working with a fresh VS Code instance 🤕

Now I can restart over and over again and STILL no auto/command completion :/
I have to dir(myobj) to get nfo about stuff. What is this!?!

my version:

Version: 1.58.0-insider (user setup)
Commit: 7dea6d7402b55671410a129661cad24b55aed9f4
Date: 2021-06-18T13:58:43.903Z (3 days ago)
Electron: 12.0.11
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: 8.9.255.25-electron.0
OS: Windows_NT x64 10.0.19043

[ewerybody]

I just had a look into the Output tab on Python Language Server there is an error saying:

[Error - 9:50:11 AM] Request textDocument/documentHighlight failed.
  Message: Request textDocument/documentHighlight failed with message: Debug Failure. Did not find evaluation scope
  Code: -32603 

maybe that's a hint? 🤷‍♀️