-
Notifications
You must be signed in to change notification settings - Fork 29
[Linter] Error running clang Error: Process execution timed out #229
Comments
Bump |
Experiencing the same error message as @dan9er now, all of a sudden. It was fine a couple of days ago, and I didn't change any Atom settings (but I may have installed some updates to macOS). |
It seems that a reboot of the machine makes it go away. Perhaps something that wasn't visible in the Activity Monitor (macOS equivalent of the Windows Task Manager) was slowing down the system. linter-clang shouldn't be this sensitive to system lag, though, so it's still a bug. |
I am facing the same issue. Rebooting my computer didn't help |
Same here. How can I increase the time limit? |
Same issue. A reboot does not help. I'm interested as well to increase the timeout limit. |
I recently started experiencing the same issue after I upgraded from Ubuntu 16.04 to 18.04. I've seen similar issues with other linting packages from a few years ago (e.g. AtomLinter/linter-shellcheck#110, AtomLinter/linter-pylint#209, AtomLinter/linter-flake8#169, though I personally have only experienced the clang and shellcheck issues), and for the packages that have attempted to address it the stopgap is to add in an option to disable execution timeouts. As discussed in AtomLinter/linter-flake8#169, this might work for those who need the longer process times, but for the relatively short files that I am editing (process execution timed out for brand new cpp files with the basic "hello world" format) this seems to be a different problem. Is there any work being done on this, or is this just a user configuration error? There was also a post on StackOverflow a few months ago with a similar issue using atom-mypy (https://stackoverflow.com/questions/60023879/process-execution-timed-out-running-linter-in-atom-for-mypy), but there has been no updates since the original post. OS: Ubuntu 18.04 |
Same issue with OS: Ubuntu 20.04 |
Same issue |
Package version: 4.1.2
Atom version: 1.19.3 x64
I get spammed with this when I type in a .cpp file.
The text was updated successfully, but these errors were encountered: