This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
Failed to activate the github package #833
Labels
Comments
|
Hi, @wryk, just to be sure — do you get the same error running in safe mode (starting Atom with )? |
|
Yep, I get exactly the same error |
|
This is also occurring on OS X in the latest beta. Atom: 1.18.0-beta0 x64 |
|
Not sure if this is of any help, but I encounter the same error when launching from terminal on OS X as well (including Atom: 1.18.0-beta0 x64 |
|
For all those who've commented about seeing this error, do any of you have |
|
In my shell I have |
|
In my terminal I managed to make atom-github work from my terminal with set NODE_ENV=production
atom |
|
I get the same result as @wryk, running |
|
@BinaryMuse I also have the value exported as |
|
Same, thats a pretty strange behavior for react... basically:
|
|
I think I have similar problem but with atom 1.18.0 First I thought that something went wrong while updating the atom but then i did a fresh install and I am getting the same error. Atom: 1.18.0 @wryk's solution also fixes the problem for me :) thanks. |
This was referenced Jun 27, 2017
|
is this being looked at? I have to swap node_env everytime I boot atom as my current project requires NODE_ENV=development! |
|
Quick fix on OS X: Locate the It's not a stable fix, but works until next update of Atom. |
|
I ran into a similar issue with Atom 1.19.0 and github 0.4.2. It turns out I had an old development version of the github apm package installed. Removing it with Atom: 1.19.0 x64 Stack TraceFailed to activate the github package CommandsNon-Core Packages |
|
Awesome find, @caged! Uninstalling that package worked for me as well. |
|
Suffering exactly the same here. I seems to be really struggling with the whole concept of NODE_ENV, though. Setting it to "production" to make Atom work seems to mean that yarn will randomly decide to remove my devDependencies, so all my webpack builds then fail... |
|
My "workaround" now is to open Atom from Finder before using the Do you know if there is a fix coming here, @smashwilson? :) |
7 tasks
|
This is silly. There's probably a ton of people out there unable to use the Github Package because they have NODE_ENV set to development but may not have the fortitude/time to look into it and stumble across this thread. I just spent an hour trying to debug this and figure it out and that's time I'm not getting back. The package shouldn't care what NODE_ENV is set to. This issue is a year old now. Please fix this. |
1 task
|
It seems like this is fixed now, @smashwilson and @BinaryMuse? At least I can open atom from the command line again with |
|
I ran into this problem, but managed to get around it by cloning using Github Desktop, then opening that directory as a project in Atom. This allowed me to login to Github using the bottom right tool. |
|
Same issue here. When I enable github package I get this error |
Same error. |
|
same for me Emitter has been disposed |
|
Same |
|
i fixed this by downloading and installing https://desktop.github.com/ maybe this can help anyone else |
|
Atom: 1.45.0 Failed to activate the github package Emitter has been disposed |
|
Same Error on my side. This happens in Safe Mode as well. Some repositories get recognized and I can commit any staged changes. Some reps do not get recognized and the git tab will stay empty. Re-Init is prevented. Removing and adding project directories again does not work. Updating Git for Windows did not help, sadly. I did not consider re-installing Git for Windows yet, as my repos are only for private matter. |
|
Atom 1.45.0 Note that this error occur even when the package seems to be activate correctly afterwards! |
|
Same error here. And my Github tab always show Offline. Atom: 1.47.0 x64 Stack TraceFailed to activate the github package CommandsNon-Core Packages |
Had the same but after a few attempts I noticed the Github tab had come alive after all. No idea when/why/how but started working again. The error remains though... |
|
Same error as all before me, but I had several tabs open with unsaved changes (About 6). Upon saving each one, Atom recognized the changes and the GitHub + Git tabs reopened |
|
Still here, still annoying as all get-out. Atom: 1.51.0 x64 Stack TraceFailed to activate the github package CommandsNon-Core Packages |
|
FWIW, I triggered the error debugging yet another instance of this: https://discuss.atom.io/t/unable-to-open-or-save-files/68842/4 |
|
Just in case if someone is only interested to get the software work, please
clean up all your atom setups and configuration. Download Atom from the
website and install it with dgkp. It should work as expected, at least work
for me.
Best,
Weiguang
…-------------------------------------------
https://weiguangcui.github.io/
On Tue, Oct 13, 2020 at 4:45 PM dnorthup-ums ***@***.***> wrote:
FWIW, I triggered the error debugging yet another instance of this:
https://discuss.atom.io/t/unable-to-open-or-save-files/68842/4
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#833 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGM4VCGUGDVVCP7YESPPURDSKRYYPANCNFSM4DLXHZVQ>
.
|
|
@weiguangcui I have had this same problem with multiple fresh installs of Atom. Besides, the purpose of an extensible editor is to save time and effort, not increase it. |
|
I think my old problem (not fully identified) may be caused by the
installation through snap with my old .atom folder is not fully clean up.
Best,
Weiguang
…-------------------------------------------
https://weiguangcui.github.io/
On Tue, Oct 13, 2020 at 9:14 PM dnorthup-ums ***@***.***> wrote:
@weiguangcui <https://github.com/weiguangcui> I have had this same
problem with multiple *fresh installs* of Atom. Besides, the purpose of
an extensible editor is to save time and effort, not increase it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#833 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGM4VCDYXK7XUR3USU7I3VDSKSYMFANCNFSM4DLXHZVQ>
.
|
|
I'm getting this when I tried to reconnect to a new github account. Ubuntu 20.04. |
|
+1 |
|
Is there any other way to add
|
|
I just caught this error while disabling the GitHub addon and trying to "reinstall it"; right after this error popped up. VersionsAtom: 1.60.0 x64 Stack TraceFailed to activate the github package CommandsNon-Core PackagesAdditional Information |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
and others
[Enter steps to reproduce:]
Atom: 1.18.0-beta0 x64
Electron: 1.3.15
OS: Microsoft Windows [version 10.0.15063]
Thrown From: github package 0.0.9
Stack Trace
Failed to activate the github package
Commands
Non-Core Packages
The text was updated successfully, but these errors were encountered: