"No symbols found in document" error in VS Code v1.67 with Modern Fortran v3.0.2022042917

[rangsimanketkaew]

Hi,

I had been using VS Code with Modern Fortran & fortls without any issues till today right before I upgraded the VS Code to the latest stable release v1.67. The issue I ran into is that the VS Code could not show the outline of the codes in the outline panel (see a snapshot below). --> "No symbols found in document"

I have tried disabling all extensions, reloading the windows, restarting the program, and even downgrading to VS Code 1.66 and v1.65v, but they didn't help. I also found this #154 and it seems that the issue I have is also from the VS Code, not Fortran extensions?

Below are the details of my environment setup:

• VS Code v1.67
• Modern Fortran v3.0.2022042917
• Fortran language server v2.3.1 (https://github.com/gnikit/fortls installed via pip)
• Python v3.9.7

Code snippets in my setting.json file:

  // Fortran
  "fortran.fortls.path": "fortls",
  "fortran.linter.extraArgs": ["-ffree-form"],
  "files.associations": {
    "*.F": "FortranFreeForm",
    "*.f": "FortranFreeForm"
  },

Any ideas to fix this issue?

[gnikit]

Can you post the output of

fortls --debug_filepath your_Fortran_file --debug_rootpath . --debug_symbols

[gnikit]

Also, please use the pre-Release version! We will be releasing version 3.0 soon, the old versions are quite outdated and problematic in all sorts of ways.

[rangsimanketkaew]

Can you post the output of

fortls --debug_filepath your_Fortran_file --debug_rootpath . --debug_symbols

Thanks for a prompt reply! Here is the output I tested your command with this source file:

Testing "initialize" request:
  Root = "."
[INFO - 14:58:07] fortls - Fortran Language Server 2.3.1 Initialized
  Successful!

  Source directories:
    /home/rketka/gitlab/cp2k/src/tmc
    /home/rketka/gitlab/cp2k/src/pw/fft
    /home/rketka/gitlab/cp2k/src/eri_mme
    /home/rketka/gitlab/cp2k/src/mpiwrap
    /home/rketka/gitlab/cp2k/src/fm
    /home/rketka/gitlab/cp2k/src/common
    /home/rketka/gitlab/cp2k/src/arnoldi
    /home/rketka/gitlab/cp2k/src/start
    /home/rketka/gitlab/cp2k/src/motion/mc
    /home/rketka/gitlab/cp2k/src/offload
    /home/rketka/gitlab/cp2k/src/subsys
    /home/rketka/gitlab/cp2k/src/emd
    /home/rketka/gitlab/cp2k/src/aobasis
    /home/rketka/gitlab/cp2k/src/motion/thermostat
    /home/rketka/gitlab/cp2k/src/hfxbase
    /home/rketka/gitlab/cp2k/src/metadyn_tools
    /home/rketka/gitlab/cp2k/src/minimax
    /home/rketka/gitlab/cp2k/src/pw_env
    /home/rketka/gitlab/cp2k/src
    /home/rketka/gitlab/cp2k/src/motion
    /home/rketka/gitlab/cp2k/src/dbcsrx
    /home/rketka/gitlab/cp2k/src/shg_int
    /home/rketka/gitlab/cp2k/src/xc
    /home/rketka/gitlab/cp2k/src/pw
    /home/rketka/gitlab/cp2k/src/input
    /home/rketka/gitlab/cp2k/src/dbm
    /home/rketka/gitlab/cp2k/src/swarm
    /home/rketka/gitlab/cp2k/src/grid
    /home/rketka/gitlab/cp2k/src/dbt/tas
    /home/rketka/gitlab/cp2k/src/base
    /home/rketka/gitlab/cp2k/src/dbt

Testing "textDocument/documentSymbol" request:
  File = "metadynamics.F"
  line    13  symbol ->   2:metadynamics                   parent = null
  line   127  symbol ->  12:metadyn_initialise_plumed      parent = metadynamics
  line   198  symbol ->  12:metadyn_finalise_plumed        parent = metadynamics
  line   225  symbol ->  12:metadyn_integrator             parent = metadynamics
  line   367  symbol ->  12:metadyn_forces                 parent = metadynamics
  line   629  symbol ->  12:metadyn_velocities_colvar      parent = metadynamics
  line   686  symbol ->  12:metadyn_position_colvar        parent = metadynamics
  line   728  symbol ->  12:metadyn_write_colvar           parent = metadynamics
  line   826  symbol ->  12:hills                          parent = metadynamics

Best,
Rangsiman

[gnikit]

Well this is strange because I am unable to replicate your issue see

Let's try the following:

1. Uninstall the extension
2. Delete the cached version of the extension (if any) in Linux it is under ~/.vscode/extensions/
   You are looking to delete *.linter-gfortran*
3. Reinstall Modern Fortran with the latest pre-release.

[rangsimanketkaew]

I followed your suggestion but, unfortunately, the issue still persists.

Best,
Rangsiman

[gnikit]

Did you restart VSCode after uninstalling Modern Fortran? If so could you try again with VSCode closed.

Also, try setting in you settings, see if something changes if not, try the other option "Both"

  "fortran.provide.symbols": "fortls"

[rangsimanketkaew]

It works, thanks for the spell!

I uninstalled all extensions and installed Modern Fortran pre-release and added "fortran.provide.symbols": "Both" to setting file.

FYI: setting the key "fortran.provide.symbols" to fortls could not solve the issue.

Best,
Rangsiman

[gnikit]

That is strange, it appears that VS Code does not recognise the symbols from the Language Server. the "Both" option turns on the fallback symbols that Modern Fortran generates.

Do any of the other features of fortls work? like hover? or GoTo variable definitions?

[rangsimanketkaew]

Just checked, unfortunately, hover does not work, nor GoTo, nor Peek.

[gnikit]

Just checked, unfortunately, hover does not work, nor GoTo, nor Peek.

That is indicative that your fortls installation is not being picked up by Modern Fortran. Could you point VS Code to the full path and see if that fixes anything (i.e. output of which fortls) by default it should be in ~/.local/bin/fortls

[gnikit]

Please also set "fortran.fortls.notifyInit": true

[rangsimanketkaew]

I already used the full path to fortls binary but it does not work.

I tried installing fortls via pip under both conda environment (/myhome/miniconda3/bin/fortls) and virtualenv (/myhome/fortls/bin/fortls) but still could not get those features (mouse hover, peek, and goto).

"fortran.fortls.notifyInit": true didn't help.

[gnikit]

Do you have conflicting settings for Modern Fortran i.e. have settings set on both the global settings.json file and your workspace settings.json file?

The problem is that fortls is not being picked up. Try and remove fortran.fortls.path from your settings. Try and play around with that until you get a popup notification that says fortls initialization complete (that is what "fortran.fortls.notifyInit": true does). We know that fortls works because of the output I made you generate before so it's just a matter of figuring out why your VS Code is struggling to find your fortls installation.

Also, please post the whole output of the log channel from Modern Fortran after having restarted VS Code
see attached image about how to find the log channel

[rangsimanketkaew]

I tested on Ubuntu, Windows, and macOS, only Windows and macOS that Modern Fortran & fortls function ok without issues. Outline can clearly distinguish between e.g. TYPE, SUBROUTINE, and FUNCTION, and I have hover, goto and peek,

but, I'm still not able to make it work on Ubuntu. I used the same settings.json for all operating systems. Not sure if there is something wrong in Python codes of fortls that is incompatible with Ubuntu (Linux) or it is just incompatibility between fortls & VS Code that occurs only on Ubuntu?