Stream: t-compiler/rust-analyzer

Topic: Workaround for #1541

David Yamnitsky (Aug 29 2019 at 13:50, on Zulip):

Hi, I am wondering if anyone has an idea of how to work around issue #1541. I am on macOS and hit it 100% of the time on my project. I confirmed using lldb as described in the issue. Is there perhaps a way to disable the language server features but still get error messages reported in vscode with cargo watch? Thanks :)

David Yamnitsky (Aug 29 2019 at 13:51, on Zulip):

The issue link above isn't right, it's

matklad (Aug 29 2019 at 13:52, on Zulip):

@David Yamnitsky to clarify, in lldb you see a thread stuck in notify? Or in chalk? We unfortunately have two different things that might cause 100% CPU

David Yamnitsky (Aug 29 2019 at 13:53, on Zulip):

one sec, double checking...

David Yamnitsky (Aug 29 2019 at 13:57, on Zulip):

It's in notify, not chalk

matklad (Aug 29 2019 at 14:03, on Zulip):

Thanks! Yeah, unfortunatelly there isn't a quick solution for this problem at the moment. I guess we should abstract away the file watching service and explore alternative backends, like watchman or vscode build-in watcher

Last update: Jul 26 2021 at 13:15UTC