Python: Go to Symbol in File Broken

[RMacfarlane]

From @rwinslow on June 11, 2018 18:39

Issue Type: Bug

Whenever I try to Go to Symbol in File I get a message "No Symbols Found". I work with a large codebase and do not need Workspace symbols, only within the file. This was working maybe a version ago but has since been broken for a couple of weeks. Disabling extensions does not help.

VS Code version: Code 1.24.0 (6a6e02cef0f2122ee1469765b704faf5d0e0d859, 2018-06-06T17:30:30.113Z)
OS version: Darwin x64 17.5.0

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-4960HQ CPU @ 2.60GHz (8 x 2600)
GPU Status	2d_canvas: unavailable_software flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: enabled rasterization: unavailable_software video_decode: enabled video_encode: enabled vpx_decode: enabled webgl: enabled webgl2: enabled
Load (avg)	2, 2, 2
Memory (System)	16.00GB (0.25GB free)
Process Argv	/Applications/Visual Studio Code.app/Contents/MacOS/Electron .
Screen Reader	no
VM	0%

Extensions (6)

Extension	Author (truncated)	Version
beautify	Hoo	1.3.1
prettify-json	moh	0.0.3
python	ms-	2018.5.0
Go	ms-	0.6.82
vscode-icons	rob	7.23.0
ayu	tea	0.14.0

(2 theme extensions excluded)

Copied from original issue: microsoft/vscode#51634

[RMacfarlane]

From @vscodebot[bot] on June 11, 2018 18:39

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• Go to Symbol - numbers on line behind name of symbol in "Go to Symbol" (#26593)
• Cannot Go to Next Symbol Highlight after Go to Symbol in File (#49743)
• "Go to Symbol in Workspace" doesn't find typescript symbols if no .ts file is open (#32054)
• 'Go to Symbol in Workspace' doesn't work unless an editor of the language is open (#23584)
• Focus current symbol when opening symbols list (#22689)

[RMacfarlane]

@rwinslow Thanks for reporting! Go to Symbol in File isn't supported out of the box for Python, the python extension adds this functionality. I'm going to move this over to their repository.

[DonJayamanne]

@rwinslow
Please could you provide the following info:

• Version of Python
• Instructions (along with a sample repo) to replicate this problem
• Check for errors in the Console window (open window Help->Toggle Developer Tools) and let us know what errors are in there.
• Please install an older version and confirm this works in an older version
  • Please uninstall the current version
  • Quit VS Code
  • Disable Autoupdating Extensions
  • Install the previous version (https://marketplace.visualstudio.com/_apis/public/gallery/publishers/ms-python/vsextensions/python/2018.4.0/vspackage)

[rwinslow]

@DonJayamanne

• Python plugin version 2018.5.0
• Local python version 3.6.1 through virtualenv
• Instructions to replicate:
  • In any Python file, press Cmd + Shift + O.
• 2018.4.0 does not fix the problem, but 2018.3.0 does. With 2018.3.0 I'm able to get the symbols to populate.
• Errors with 2018.5.0:

console.ts:136 [Extension Host] Python Extension: sendCommand jediProxy, Error (sendCommand) This socket has been ended by the other party

console.ts:136 [Extension Host] Error: This socket has been ended by the other party
	at Socket.writeAfterFIN [as write] (net.js:305:12)
	at JediProxy.<anonymous> (/Users/richwinslow/.vscode/extensions/ms-python.python-2018.5.0/out/client/providers/jediProxy.js:180:33)
	at Generator.next (<anonymous>)
	at fulfilled (/Users/richwinslow/.vscode/extensions/ms-python.python-2018.5.0/out/client/providers/jediProxy.js:12:58)
	at <anonymous>
t.log @ console.ts:136
t._logExtensionHostMessage @ extensionHost.ts:393
(anonymous) @ extensionHost.ts:210
emitTwo @ events.js:106
emit @ events.js:194
process.nextTick @ internal/child_process.js:766
_combinedTickCallback @ internal/process/next_tick.js:73
_tickCallback @ internal/process/next_tick.js:104

• There are no errors with 2018.3.0
• Also, VSCode settings

{
    "editor.fontFamily": "DejaVu Sans Mono, monospace",
    "editor.fontSize": 15,
    "editor.minimap.enabled": true,
    "editor.minimap.renderCharacters": true,
    "editor.minimap.showSlider": "always",
    "editor.renderIndentGuides": true,
    "editor.renderWhitespace": "boundary",
    "extensions.autoUpdate": false,
    "problems.decorations.enabled": true,
    "files.trimTrailingWhitespace": true,
    "files.exclude": {
        "**/*.pyc": true
    },
    "git.decorations.enabled": true,
    "go.formatTool": "gofmt",
    "python.linting.pylintArgs": [
        "--disable=W0703,R0913,E1101,W0212,W0201,C0103,C0111,W1202,R0903,W1401,R0201"
    ],
    "python.pythonPath": "/Users/richwinslow/Envs/sojern/bin/python",
    "python.venvPath": "/Users/richwinslow/Envs/sojern",
    "python.workspaceSymbols.enabled": false,
    "terminal.external.osxExec": "iTerm.app",
    "workbench.activityBar.visible": true,
    "workbench.startupEditor": "newUntitledFile",
    "vsicons.dontShowNewVersionMessage": true,
    "workbench.iconTheme": "vscode-icons",
    "workbench.colorCustomizations": {
        "editorIndentGuide.activeBackground": "#777777"
    },
    "extensions.ignoreRecommendations": true,
    "window.zoomLevel": 0,
    "workbench.colorTheme": "Ayu Mirage",
}

[DonJayamanne]

@rwinslow

• Instructions (along with a sample repo) to replicate this problem

Please could you provide some sample code.

[rwinslow]

@DonJayamanne
This code was able to exhibit the issue. https://github.com/rwinslow/vscode1931

• Instructions
  • With the file open and using Python plugin version 2018.5.0, press Cmd + Shift + O. The dropdown menu that appears says "No Symbols Found".
  • Can also replicate by choosing "Go to Symbol in File" from the Menu or in the Cmd + Shift + P quick menu.

I've also added screenshots to the repo showing the failure with 2018.5.0 and success with 2018.3.0

If you need additional instructions, please let me know what steps you'd like to see.

[brettcannon]

I can't reproduce:

We must have fixed it between 2018.5.0 and now, so this should be fixed in the next release.

[rwinslow]

@brettcannon just saw the update to 2018.6.0 and installed it. Issue still hasn't been fixed in the latest version. Also having the issue on another computer. Both are running Mac OS High Sierra 10.13.5.