question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Build workspace symbol does not work for me since 2019.11.50794

See original GitHub issue

Environment data

  • VS Code version: XXX
  • Extension version (available under the Extensions sidebar): 2020.2.63072. However it seems that all the version past 2019.11.50794 are affected
  • OS and version: Fedora 31
  • Python version (& distribution if applicable, e.g. Anaconda): I tried this with many different version of python virtualenvs, from 2.7 to 3.7
  • Type of virtual environment used (N/A | venv | virtualenv | conda | …): venv
  • Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): jedi
  • Value of the python.languageServer setting: I was only able to find setting python.autoUpdateLanguageServer and it’s set to true

Expected behaviour

The “Build workspace symbol” action should work, at least when called explicitly

Actual behaviour

That action does not work. I inspect the Python output in VS Code and it seems that ctags binary hasn’t been called at all

Steps to reproduce:

I don’t really know how to specifically reproduce it. I just know that I was not using VS Code for a while (stopped in October 2019). Then I came back to it in February 2020 and updated python extension. From that point, “Build workspace symbols” hasn’t been working for me. Here are all the things that I tried:

  • Disable GitLens extension
  • Disable all the other extensions except for Python
  • Reinstall VS Code while also purging all the configuration
  • I even ran ctags manually but VS Code wouldn’t pick up the generated symbols when I searched for them using Ctrl+T
  • I tried using different virtualenvs with different python versions, none of them seemed to work

The only thing that worked for me in the end was to iterate through recent version of python extension. I found out that version 2019.11.50794 works for me, while 2020.1.57204 does not. So I’m sticking with 2019.11.50794 for now

This is what happens (or rather does not happen) in 2020.2.63072: not_working

Downgrading to 2019.11.50794: working

Logs

Python output when trying to run “Build workspace symbols” with 2020.2.63072: https://pastebin.com/raw/Fsnc2UEB Python output when running “Build workspace symbols” with 2019.11.50794: https://pastebin.com/raw/CWSd7y3y

If any other output is required, please let me know!

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:7 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
cdfullercommented, Feb 13, 2020

Do you have python.workspaceSymbols.enabled set to true? #10092

0reactions
ericsnowcurrentlycommented, Mar 3, 2020

That’s great to hear! Sorry you had a problem in the first place.

Read more comments on GitHub >

github_iconTop Results From Across the Web

`ctags` has no `options` argument, cannot build workspace ...
The extension is designed to work with exuberant ctags which is probably where you're having issues. As for specifying a path to ctags, ......
Read more >
in system2("jupyter", c("kernelspec", "--version"), false, false)
The command to setup IRkernel has to be run in the same environment as the jupyter installation. Due to this, It won't work...
Read more >
Vs Code - Why Is My Jupyter Notebook Ui A Bit Different From ...
After choosing a method you are provided with parameter info. If the problem persists consult the language extension's documentation.
Read more >
vimspector from puremourning - Coder Social
Vimspector should work for any debug adapter that works in Visual Studio Code. ... Because the author doesn't use neovim regularly, and there...
Read more >
Cyberbrain: Python debugging, redefined. - PythonRepo
At this point, you should NOT use Cyberbrain in production. ... and nothing happened and the terminal keeps telling me Can't connect to...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found