Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ToolchainLanguageServerCrashHandler to handle crashes #178

Closed
wants to merge 1 commit into from

Conversation

DavidGoldman
Copy link
Collaborator

The handler will be responsible for handling the crash:

  • Inform the user of the crash
  • Log the crash
  • Choosing to restart the ToolchainLanguageServer or
    disabling it

The handler will be responsible for handling the crash:
- Inform the user of the crash
- Log the crash
- Choosing to restart the `ToolchainLanguageServer` or
  disabling it
@benlangmuir
Copy link
Member

@swift-ci please test

Copy link
Member

@benlangmuir benlangmuir left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's hard to review this without having a more complete picture of how the crash handler will actually re-initialize the document state. What do you think of adding that support here?

///
/// The handler may or may not chose to re-open previously open documents and/or
/// stop sending any further requests to the given `ToolchainLanguageServer`.
func handleCrash(_ languageService: ToolchainLanguageServer, _ debugInfo: String)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the idea for the debug info parameter? Right now I see it's always a fixed string - where would we get more information to pass here?

@DavidGoldman
Copy link
Collaborator Author

Closing since this is no longer a priority (may re-open later)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants