-
Notifications
You must be signed in to change notification settings - Fork 7.6k
NodeConnection.js question #6491
Comments
@zaggino - I don't think we've seen this commonly, but from looking at the code it looks like it would happen if there were something wrong with the brackets-node process - for example, if some other previously loaded node module had thrown an uncaught exception. (Note that this shouldn't have to do with a node.js that users themselves installed - this would be about the node that's packaged with Brackets which we automatically launch on startup.) It would help to get more information from your users who are seeing the problem - do you have some bug numbers in your bugbase you could point us to? Additionally, if we could get dumps of your users' Brackets console logs (by having them do Debug > Show Developer Tools and copying out the console), that would help, since I believe all output from the node process's console is echoed back into the Brackets console. Assigning to @jasonsanjose to investigate further, medium priority. |
@njx Not a lot of info I've been able to get from users (adding "Report a bug" button made much more people report stuff, but the level of response is very low). I was just curious because it seems to appear over and over again and I was never able to replicate it. Quite a collection of the issues with this (without much usable information): |
As @medimatrix suggested in brackets-userland/brackets-git#76, this may be related to #6282 |
@njx @jasonsanjose After gettling latest master from both This is Brackets startup log, my only file there is
|
Reassigned to @bchintx. @zaggino does this only happen on windows? I don't see anything suspicious in the stack trace. I assume |
@zaggino if you're only seeing this when building on Windows, then you might need to check out @JeffryBooher 's comment here. In a nutshell, the latest changes require that we rename 'Brackets-node.exe' back to 'node.exe'. As a result, you'll need to be sure to delete your intermediate folder BTW, this should only have happened in the last few days. It doesn't address the original issue described above, which seems to be reported before we change the filename. |
@bchintx You were right, it was related to what @JeffryBooher was talking about and not related to the original problem. Fixed now with |
@zaggino Glad to hear it works for you. BTW, you won't need to worry about this again, unless you checkout a commit prior to our change to rename 'node.exe'. Still not sure what caused your originally reported issue though. Unfortunately, that error message could result from a variety of problems. |
Closing this issue as |
👍 agree, I haven't seen this issue in a while now |
@VinuOye try disabling all the firewalls and antiviruses you have to see if it helps. |
What are the common reasons for
Max connection attempts reached
message when trying to connect to Node.JS?https://github.com/adobe/brackets/blob/master/src/utils/NodeConnection.js#L309
On my computer, this works every time (and on any computer that I've tried...) so I'm not able to replicate this error but many users got this error and some claim to have Node.JS properly installed. Any idea? @jasonsanjose @joelrbrandt
The text was updated successfully, but these errors were encountered: