Skip to content

Language Server: Outline says No Symbols Found for the current doc. start type and symbols appear #2334

Closed

Description

@derekwallace

Insiders latest build

No symbols shown for the current . Will stay like this forever.
image

As soon as i start to type in the doc the Outline is updated.
The outline should reflect the current doc that is open.
image

Activity

  1. ericsnowcurrently commented on Aug 6, 2018

    @ericsnowcurrently

    Hi derekwallace. Thanks for letting us know about this. Unfortunately, I was no able to reproduce the problem. I simply opened a folder I've used in the past and the outline loaded without me doing anything else. What would be the simplest way to reproduce the problem? Thanks!

    FWIW, this could be related to #2112 (though probably not).

  2. derekwallace commented on Aug 6, 2018

    @derekwallace
    Author

    Hi, unfortunately this is a common scenario. The issue is not easily reproducible.

    At a minimum the outline should have a refresh button to force the display.

  3. MikhailArkhipov commented on Aug 7, 2018

    @MikhailArkhipov

    The problem is VSC asks for symbols right after the file is open and code analysis hasn't completed yet. There is not easy way to tell VSC that analysis complete and it should ask again.

  4. DonJayamanne commented on Aug 7, 2018

    @DonJayamanne

    The problem is VSC asks for symbols right after the file is open and

    Shouldnt we just not return anything, instead wait for the analysis to completed and return once completed. Kind of a wait with a timeout (timeout when the request is cancelled via the cancellation token).

  5. patrys commented on Aug 7, 2018

    @patrys

    Or return an unresolved Promise?

  6. DonJayamanne commented on Aug 7, 2018

    @DonJayamanne

    Or return an unresolved Promise?

    Yes, technically thats what we should do (in nodejs that's the way to wait and return).

  7. MikhailArkhipov commented on Aug 9, 2018

    @MikhailArkhipov

    Don Jayamanne (@DonJayamanne)
    "Shouldnt we just not return anything, instead wait for the analysis to completed"

    No. Analysis can take long time and for sync reasons we can't wait or you won't see completions. We process VSC requests sequentially or else it is a mess with text buffer change coming AFTER request for completion for that change. Therefore request does not get handled until the previous one returns.

    We do can wait 'reasonable' time for this file analysis completion.

  8. DonJayamanne commented on Aug 12, 2018

    @DonJayamanne

    No. Analysis can take long time and for sync reasons we can't wait or you won't see completions.

    Ok then, shouldn't this outline take precedence over analysis?

    From what I've seen analysis takes a long time depending on project size and when using anaconda environments. In such cases we can't just wait for analysis to complete.
    Certain things will have to take precedence over analysis. Unless of course, analysis is necessary for the outline.

    Long story short, what's our long term solution for this problem?
    Please note, outline will be critical, VSC has added a breadcrumbs navbar as well (in the insides build). Code lenses for test methods rely on the outline too.

  9. MikhailArkhipov commented on Aug 21, 2018

    @MikhailArkhipov

    microsoft/PTVS#4645 made possible proper async execution. This does not make outline appear faster as it is waiting for analysis but other functionality is not blocked. Outline window displays 'loading symbols...'

  10. MikhailArkhipov commented on Aug 23, 2018

    @MikhailArkhipov
  11. aarshtalati commented on Aug 29, 2018

    @aarshtalati

    I am on stable x86 version 1.26.1 (Commit: 493869ee8e8a846b0855873886fc79d480d342de) on Ubuntu 18.04 LTS. I checked and mine is the lastest version. I am experiencing the same issue. I tried typing and created Python class in my currently open file. Still, I am getting "No Symbols Found for the <current_file>.py" message.

  12. brettcannon commented on Aug 29, 2018

    @brettcannon
    Member

    @ablaze8 your issue is different than this one. Please open a new issue.

  13. aarshtalati commented on Aug 30, 2018

    @aarshtalati

    #57638

  14. afeblot commented on Aug 30, 2018

    @afeblot

    For the record, here it is: #2468

  15. locked as resolved and limited conversation to collaborators on Oct 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

area-intellisenseLSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc.bugIssue identified by VS Code Team member as probable bug

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions