Fix pylint hang on file with many errors #380
Merged
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.
When pylint reports a large number of messages on a given file (200 should be sufficient on Linux), the returned output can exceed the maximum buffer size available to a pipe causing a deadlock as the pylint plugin waits for the pylint process to complete, while the pylint process waits for the pylint plugin to clear out the pipe. This hangs the pylint plugin and no linting is ever provided for the file.
This bug only exists when the plugin lints files from the file system and is not an issue when pylsp.plugins.pylint.executable has been configured due to a different code path being used.