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 a restartAfterCrash option #108

Merged
merged 3 commits into from
Jan 11, 2021
Merged

Add a restartAfterCrash option #108

merged 3 commits into from
Jan 11, 2021

Conversation

hokein
Copy link
Collaborator

@hokein hokein commented Nov 24, 2020

Allowing us to control the maximum clangd restart times (by default it is 4), this would make the life of tracking/reporting crashes a bit easier.

Copy link
Member

@sam-mccall sam-mccall left a comment

Choose a reason for hiding this comment

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

This make a lot of sense for those of us that really want to track down/report crashes.

I think we can simplify the option a little though.

package.json Outdated Show resolved Hide resolved
Allowing us to control the maximum clangd restart times (by default it is 4), this
would make the life of tracking/reporting crashes a bit easier.
@hokein hokein force-pushed the expose-max-restart-count branch from 96bc005 to 02236a2 Compare January 11, 2021 08:30
@hokein hokein force-pushed the expose-max-restart-count branch from 02236a2 to bb76863 Compare January 11, 2021 08:30
@hokein hokein changed the title Add a maxRestartCount option Add a restartAfterCrash option Jan 11, 2021
@hokein hokein merged commit 35c0877 into master Jan 11, 2021
@hokein hokein deleted the expose-max-restart-count branch January 11, 2021 08:34
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.

2 participants