-
Notifications
You must be signed in to change notification settings - Fork 39
[1.1.3] Linter does not lint #151
Comments
Did you restart Atom after the upgrade? |
I've restarted atom and my computer with no luck. When I save, a bunch of new atom processes are created and don't seem to get ended. |
What CLI args are they spawned with? Does Windows Task Manager show that? |
I can't check that from the Task manager, but I could put a breakpoint on the code that spawns the process. I put a breakpoint on the execNode function in helpers.coffee and the args created was this ["--reporter", "C:\Users\bhromano.atom\packages\linter-jshint\node_modules\jshint-json\json.js", "--filename", "C:\path\to\my\file.js", "-"] If you would like me to put a breakpoint somewhere else I could try that. |
All seems perfect, can you create a dummy js file and point
and then post the output? |
Sorry. I don't follow. I should create a file with just that one line and have the linter run over the file? |
A one lined file, and pass it's absolute path instead of jshint exe in linter-jshint |
I replaced filePath with the dummy file and i got the Invalid result error message |
Maybe it's a problem with end-of-stream detection, jshint keeps waiting for new input even when we have provided it the whole file, was it working for you before the update? |
No. I've been receiving the invalid results error since the last version. I've got to get back to some other stuff, but I'll be avaiable to help again in an about an hour or so. |
I can confirm I have the same problem after the update. The linter stopped working. |
@greven was it working for you before the update? |
2 Updates before, yes fine, without a problem. 1 Update before I was getting the Path Error bug, even though I could spawn jshint from the cmd line. After this update, no longer get the Path error, but it doesn't work also, i.e., doesn't lint anything, I tried with a .jshintrc file and without, same result. |
@greven could you please post your |
Here is my process.env.Path. I doubt it contains anything useful.
|
Oh sorry, I meant the whole |
https://gist.github.com/benjaminRomano/cde5557d1bba1d77ea84 Here is my process.env |
I just ran jshint from command line and it hangs when I use these paramters
It runs with these parameters successfully:
|
That's because we are using stdin and while using stdin, it expects us to write the contents of the file to it, which is what we do. |
My process.env is here: http://pastebin.com/QHPuqYjy |
I have a solution for this I believe. It is a problem with atom-linter. I created the issue in that project. steelbrain/atom-linter#21 |
Guys, I need someone to confirm that this patch to |
Yes that worked. Thanks @benjaminRomano and @steelbrain |
@steelbrain , It works too ! Thanks. |
Fixed by steelbrain/atom-linter#22 |
I can confirm that last update fixed it for me. |
After the new update, I no longer get the error Invalid Result received from JSHint, but now the file does not seem to actually get checked by the linter anymore. This is on a windows environment and I've tried re-installing linter-jshint with no luck.
If you need any other info, please let me know.
The text was updated successfully, but these errors were encountered: