-
Notifications
You must be signed in to change notification settings - Fork 103
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
harper-ls --stdio using too many threads #198
Comments
This should be configured by tokio to be the number of cores on your machine, how many do you have? |
I probably have around 128 cores. Do you know how to configure this using? I definitely do not think the program should be allowed to use all the cores. It should be limited to 2, at most 3. I am seeing the same problem with pyright, BTW. |
Ah. This should be a simple fix. We'll set |
@grantlemons drafted a fix and it has been merged. I'm going to spend some time with Harper this afternoon to make sure everything checks out before creating a release. At that point, you can confirm that the problem is fixed. |
@grantlemons Thanks, could you please make another tag, 0.12.0? I am using Mason and this seems to download the latest tag. |
Sorry it took so long to get back to you on this. The Mason maintainer is extremely unresponsive when it comes to PRs. You should be able to get a new version now. Would you mind confirming whether your issue has been fixed? |
I'm assuming we're good here. Thanks for letting us know about the problem! |
Hi @elijah-potter thanks. I am having other issues with neovim, this time memory issues, but I think I haven't really seen any problem with this plugin lately, so I assume the update fixed the issue. |
I'm sorry about the other issues, but I'm glad Harper's working. Thanks again! |
Hi,
I just downloaded this with Mason and I am using it with neovim. I suddenly found out that I cannot spawn threads and when I check with htop I see that harper-ls is using about 150 theads:
Why is this happening? How can I configure this tool to use only one thread?
Cheers.
The text was updated successfully, but these errors were encountered: