Skip to content

add more context on why LSP server start failed. #19626

Closed
#20821
Closed
add more context on why LSP server start failed.#19626
#20821
Assignees
karthiknadig
Labels
area-internalLabel for non-user facing issuesfeature-requestRequest for new features or functionalityneeds PRReady to be worked onverifiedVerification succeeded
Milestone
March 2023

Description

@heejaechang
Heejae Chang (heejaechang)
opened on Aug 3, 2022

Currently, we only get callstack when it failed, but the callstack is very generic and same for all causes, so no actionable data except the fact it got failed.

it would be very helpful if it contains other context such as why LSP server is started (interpreter changes, from status bar or command palette, trusted/untrusted? folder or single file mode, restart command is issued, local or remote, what kind of remote and etc)

anything that can inform us code path it took to start new server so we can repro the failure.

Activity

  1. Heejae Chang (heejaechang)
    added
    feature-requestRequest for new features or functionality
    on Aug 3, 2022
  2. github-actions
    added
    triage-neededNeeds assignment to the proper sub-team
    on Aug 3, 2022
  3. Karthik Nadig (karthiknadig)
    self-assigned this
    on Aug 4, 2022
  4. Karthik Nadig (karthiknadig)
    added
    needs PR
    area-internalLabel for non-user facing issues
    on Aug 4, 2022
  5. Karthik Nadig (karthiknadig)
    added this to the August 2022 milestone on Aug 4, 2022
  6. Kartik Raj (karrtikr)
    removed
    triage-neededNeeds assignment to the proper sub-team
    on Aug 5, 2022
  7. github-actions
    removed
    needs PR
    on Aug 9, 2022
  8. Kartik Raj (karrtikr)
    added
    needs PRReady to be worked on
    on Aug 9, 2022
  9. Karthik Nadig (karthiknadig)
    modified the milestones: August 2022, September 2022 on Aug 23, 2022

  10. heejaechang commented on Aug 29, 2022

    @heejaechang
    Heejae Chang (heejaechang)
    on Aug 29, 2022
    Author

    Karthik Nadig (@karthiknadig) any progress?

  11. karthiknadig commented on Aug 29, 2022

    @karthiknadig
    Karthik Nadig (karthiknadig)
    on Aug 29, 2022
    Member

    Sorry, no. I could not get to this for august.

  12. Karthik Nadig (karthiknadig)
    modified the milestones: September 2022, October 2022 on Sep 26, 2022
  13. Karthik Nadig (karthiknadig)
    modified the milestones: October 2022, November 2022 on Oct 24, 2022
  14. Brett Cannon (brettcannon)
    modified the milestones: November 2022, January 2023 on Nov 28, 2022
  15. Karthik Nadig (karthiknadig)
    modified the milestones: January 2023, February 2023 on Jan 23, 2023
  16. Karthik Nadig (karthiknadig)
    modified the milestones: February 2023, March 2023 on Feb 21, 2023
  17. Karthik Nadig (karthiknadig)
    closed this as completedin #20821on Mar 9, 2023
  18. Karthik Nadig (karthiknadig)
    added a commit that references this issue on Mar 9, 2023

    Restart reason telemetry event for `pylance` (#20821)

    b897300
  19. Karthik Nadig (karthiknadig)
    added
    verifiedVerification succeeded
    on Mar 20, 2023
  20. github-actions
    locked as resolved and limited conversation to collaborators on Apr 20, 2023
  21. Wes McKinney (wesm)
    added 2 commits that reference this issue on Mar 28, 2024

    Merged PR posit-dev/positron-python#58: Merge latest upstream

    691ce83

    Merged PR posit-dev/positron-python#58: Merge latest upstream

    26cb473
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area-internalLabel for non-user facing issuesfeature-requestRequest for new features or functionalityneeds PRReady to be worked onverifiedVerification succeeded

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions