Skip to content

fix(vscode): force lsp to be single worker#5050

Merged
benfdking merged 1 commit intomainfrom
force_lsp_to_be_single_threaded
Jul 28, 2025
Merged

fix(vscode): force lsp to be single worker#5050
benfdking merged 1 commit intomainfrom
force_lsp_to_be_single_threaded

Conversation

@benfdking
Copy link
Contributor

No description provided.

@benfdking benfdking changed the title fix(vscode): force lsp to be single worker) fix(vscode): force lsp to be single worker Jul 28, 2025
@benfdking benfdking requested a review from Copilot July 28, 2025 19:09
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR fixes an issue with the VSCode Language Server Protocol (LSP) implementation by forcing it to use a single worker thread instead of the default multi-worker configuration.

  • Forces the LanguageServer to use max_workers=1 parameter

@benfdking benfdking force-pushed the force_lsp_to_be_single_threaded branch 4 times, most recently from 1e5a494 to c3ffb60 Compare July 28, 2025 21:51
@benfdking benfdking force-pushed the force_lsp_to_be_single_threaded branch from c3ffb60 to 8b2c0ba Compare July 28, 2025 21:51
@benfdking benfdking merged commit a94c4f0 into main Jul 28, 2025
27 checks passed
@benfdking benfdking deleted the force_lsp_to_be_single_threaded branch July 28, 2025 22:12
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