-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to activate the atom-hg package #47
Comments
Looks like going from Atom 1.14 to Atom 1.15 breaks the entire plugin... Hoping to get a look in later this week(end?) |
Couldn't resist having a short look. This looks like a false alarm. I'm having the exact same problem, but that's because I suspect @goemaeret is running my fork, and not the actual package. Line 6 in atom-hg.coffee is empty in all released versions, but line 6 in atom-hg.coffee of my fork contains a quick & dirty proxy I was using to track the performance of all calls to the atom-hg plugin (which indeed calls Object.parse on a far-from-stable location). So I suspect the solution is to switch back to the atom-hg you get from apm install. |
@TomKemperNL Actually after reinstalling the package the problem is solved. It was indeed the forked version that caused this behaviour. So all is good :) Thx for looking into it! |
Thanks for the feedback, guys! |
I have the same issue. I installed and reinstall but it does not works. Atom: 1.34.0 x64 Stack TraceFailed to activate the atom-hg package
Commands
Non-Core Packages
|
Thank you for contributing with this stack trace report, @albertcito. I have created another issue (#55) since it looks like the exception behind this startup error is slightly different. |
Atom: 1.15.0 x64
Electron: 1.3.13
OS: Mac OS X 10.12.3
Thrown From: atom-hg package 2.0.11
Stack Trace
Failed to activate the atom-hg package
The text was updated successfully, but these errors were encountered: