-
Notifications
You must be signed in to change notification settings - Fork 45
Error: Process execution timed out #169
Comments
You should only be hitting this if Does |
No it doesn't, it runs fast, its rare, I mean it is not as frequent as my
previous reported issue.
I really don't think that in a ruby project I had to face this problems
when this doesn't happen in a python one, I do both.
Thanks
|
I'm adding an option that disables throwing the error, most likely what is going on is a process is getting stuck (for whatever reason), everything else moves on, and then after a bit it's getting killed and throwing this... which we don't really care about. |
Thanks! |
I'm also having this issue, when flake8 runs fine from terminal. I've also noticed that this is an issue with https://github.com/AtomLinter/linter-phpcs/ and https://github.com/AtomLinter/linter-csslint/. All three of these projects seem to have the issue in the same file
|
I am having this issue , anytime it lints python file. Flake8 runs perfectly fine in terminal. |
Also it fails to do any code analysis. |
@Arcanemagus is there any way the AtomLinter team can look into this, given that it's happening in multiple linters? |
@ryanisnan I'm actually working on the PR I was talking about earlier, sorry about the delay. For most linters this isn't an issue, for a few that need to legitimately run for that long an option should be provided, for most where this is triggering though it's a sign that the linter itself is getting stuck running for some reason. As this particular linter seems to fall into both of the latter categories I'm simply going to provide an option that disables the timeout if the user desires. |
Thanks for the reply @Arcanemagus. I'm interested to see the PR, however, I do not think that the runtime of flake8 is the issue. Given your comments, I think we are solving the wrong problem (at least in my instance, and others in the thread). I can run flake8 just fine from terminal on the current file I'm working in, which is 1146 lines long, sub 1 second. Saving the file from within Atom triggers the There very likely is a use-case for linters that do take longer and would require the work you're proposing, but I have no reason to suspect that this is the issue being discussed here. |
Also, given that it is happening to some people and not others, it is possibly an environment-specific issue (Atom can't find the linter, permission issue perhaps, etc.). I would love to help debug the issue in any way possible, but am an atom newb. |
|
|
Can you try out the latest master, enable the new option, and see if you get any results? To do that: git clone https://github.com/AtomLinter/linter-flake8.git
cd linter-flake8
apm install
apm uninstall linter-flake8
apm link Then restart/reload Atom. To switch back to the regular version: cd linter-flake8
apm unlink
apm install linter-flake8 |
@Arcanemagus Just tried that. Enabled the new Disable Timeout setting, made some changes that should have caused different flake8 errors, saved the file, waited ~20 seconds, and received no linting. TIL about |
@Arcanemagus as you may not be able to replicate the issue, let me know if I can help in any way. ryanisnan on freenode. |
@ryanisnan Can you place a breakpoint here and see if it is ever returning? 😕 |
Marking as closed since the initial error would be fixed by the option and there was never a response to the secondary issue. |
Confirmed fixed. |
@Arcanemagus |
After reinstalling linter-flake8, #168 was fixed, but now appears this.
OSX 10.11.3
Atom 1.6.0-beta7
The text was updated successfully, but these errors were encountered: