search

brackets-userland / brackets-npm-registry

Extension to install other extensions with npm
MIT License
44 stars 8 forks source link

ExpectedError: Error: Max connection attempts reached #24

Closed chandrakantaS closed 8 years ago

chandrakantaS commented 9 years ago

I am using this extension for brackets to use eslint extension. But after installing this m facing the problem screenshot from 2015-08-03 17-55-29

zaggino commented 9 years ago

Do you have any errors in the console? Did the npm install finish without any errors? Try running gulp build in the directory of this extension and make sure it passed.

chandrakantaS commented 9 years ago

npm install and gulp build both finished successfully inside brackets-npm-registry extension directory. I m seeing this error while creating any file with .js extension & an es-lint error also.

screenshot from 2015-08-04 14-08-23

chandrakantaS commented 9 years ago

screenshot from 2015-08-04 14-13-02

zaggino commented 9 years ago

Any error in the brackets console? Debug -> Show developer tools -> Console This connection problem is usually caused by failing extension.

chandrakantaS commented 9 years ago

Now I just Uninstalled everything and re-installed brackets-npm-registry. Seeing this error in console:

screenshot from 2015-08-04 18-19-57

zaggino commented 9 years ago

Can't see anything there. This is worth reading though: https://github.com/zaggino/brackets-git/issues/1109 https://github.com/zaggino/brackets-git/issues/410 https://github.com/zaggino/brackets-git/issues/468

chandrakantaS commented 9 years ago

Is this something wrong?? Got this error in brackets console while installing zaggino.brackets.git

[node-log 3:47:06 PM] { [Error: ENOENT, no such file or directory '/home/chandra/.config/Brackets/cef_data/f_0001be'] errno: 34, code: 'ENOENT', path: '/home/chandra/.config/Brackets/cef_data/f_0001be', syscall: 'open' }

Blind write attempted: /home/chandra/.config/Brackets/state.json 1438769844000 null

zaggino commented 9 years ago

I've never seen that one, did it install fine?

chandrakantaS commented 9 years ago

Yes, installed successfully. And again I have installed all extensions from brackets-npm-registry. It seems to work fine now. I am not seeing any error any more.

vkkotha commented 9 years ago

I had the same issue recently and Killing Brackets.app/Contents/node-core process and restarting Brackets seems to fix this issue on my Mac.

aparvezbd commented 7 years ago

I have found the problem in console. How can I solve it? screenshot_1