Repository navigation
fix(typescript-plugin): fault tolerance for named pipe servers json file - #4075
Merged
Merged
Conversation
Member
|
Thanks! This may be caused by multiple tsserver processes overwriting json files at the same time. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
After the upgrade, I suddenly found that the syntax in the
templatewas invalid, and then tracked the problem and found that there was a problem reading the file insearchNamedPipeServerForFile. The format may have been broken when writing a certain version, resulting in JSON here. WhenJSON.parse, an error is reported directly, but no interception is done, and then there is no code prompt. I donβt know if I should delete the temp file directly when there is a problem withparse. At present, I have addedtry {} catch (e) {}to solve the problem.The following is the format of the file that I found during troubleshooting.
