Github integration not working


#1

I have tried everything and cannot get the github integration to work. No matter what I do, the git and github panes both remain blank. I’ve tried 1.18 and 1.19 beta. I have completely (COMPLETELY) removed all traces of atom from my machine and re-installed atom. Nothing.

Git works perfectly fine from the terminal, but will not work at all inside atom.

Atom 1.18
Git 2.13.1.2
Windows 7 SP1

Any help would be greatly appreciated before I lose my mind.

PS, I’m not sure if it’s relevant, but if I open up an empty session in atom and click ‘create repository’ in the git pane, it opens a message box and asks for a location to init a repo. If you click ‘init’, a blank folder is created at the location given, but nothing else happens. The message box never closes and the folder remains blank.

Here is the dev tools error log (running 1.19 beta):

Uncaught (in promise) Error: spawn UNKNOWN
    at exports._errnoException (util.js:1022:11)
    at ChildProcess.spawn (internal/child_process.js:313:11)
    at exports.spawn (child_process.js:399:9)
    at Object.exports.execFile (child_process.js:160:15)
    at Object.module.(anonymous function) [as execFile] (ELECTRON_ASAR.js:200:20)
    at C:\Users\conwelps\AppData\Local\atom\app-1.19.0-beta1\resources\app\node_modules\dugite\build\lib\git-process.js:65:52
    at Function.exec (C:\Users\conwelps\AppData\Local\atom\app-1.19.0-beta1\resources\app\node_modules\dugite\build\lib\git-process.js:48:16)
    at Proxy.executeGitCommand (C:\Users\conwelps\AppData\Local\atom\app-1.19.0-beta1\resources\app\node_modules\github\lib\git-shell-out-strategy.js:343:54)
    at C:\Users\conwelps\AppData\Local\atom\app-1.19.0-beta1\resources\app\node_modules\github\lib\git-shell-out-strategy.js:214:48
    at Generator.next (<anonymous>)
    at step (C:\Users\conwelps\AppData\Local\atom\app-1.19.0-beta1\resources\app\node_modules\github\lib\git-shell-out-strategy.js:74:197)
    at C:\Users\conwelps\AppData\Local\atom\app-1.19.0-beta1\resources\app\node_modules\github\lib\git-shell-out-strategy.js:74:443
    at C:\Users\conwelps\AppData\Local\atom\app-1.19.0-beta1\resources\app\node_modules\github\lib\git-shell-out-strategy.js:74:105
    at Promise (C:\Users\conwelps\AppData\Local\atom\app-1.19.0-beta1\resources\app\node_modules\github\lib\git-shell-out-strategy.js:311:30)
    at C:\Users\conwelps\AppData\Local\atom\app-1.19.0-beta1\resources\app\node_modules\github\lib\git-shell-out-strategy.js:212:20
    at Generator.next (<anonymous>)
    at step (C:\Users\conwelps\AppData\Local\atom\app-1.19.0-beta1\resources\app\node_modules\github\lib\git-shell-out-strategy.js:74:197)
    at C:\Users\conwelps\AppData\Local\atom\app-1.19.0-beta1\resources\app\node_modules\github\lib\git-shell-out-strategy.js:74:443
    at C:\Users\conwelps\AppData\Local\atom\app-1.19.0-beta1\resources\app\node_modules\github\lib\git-shell-out-strategy.js:74:105
    at C:\Users\conwelps\AppData\Local\atom\app-1.19.0-beta1\resources\app\node_modules\github\lib\async-queue.js:26:44
    at Generator.next (<anonymous>)
    at step (C:\Users\conwelps\AppData\Local\atom\app-1.19.0-beta1\resources\app\node_modules\github\lib\async-queue.js:7:197)
    at C:\Users\conwelps\AppData\Local\atom\app-1.19.0-beta1\resources\app\node_modules\github\lib\async-queue.js:7:443
    at C:\Users\conwelps\AppData\Local\atom\app-1.19.0-beta1\resources\app\node_modules\github\lib\async-queue.js:7:105
    at Task.execute (C:\Users\conwelps\AppData\Local\atom\app-1.19.0-beta1\resources\app\node_modules\github\lib\async-queue.js:31:13)
    at C:\Users\conwelps\AppData\Local\atom\app-1.19.0-beta1\resources\app\node_modules\github\lib\async-queue.js:96:26
    at Generator.next (<anonymous>)
    at step (C:\Users\conwelps\AppData\Local\atom\app-1.19.0-beta1\resources\app\node_modules\github\lib\async-queue.js:7:197)
    at C:\Users\conwelps\AppData\Local\atom\app-1.19.0-beta1\resources\app\node_modules\github\lib\async-queue.js:7:443
    at C:\Users\conwelps\AppData\Local\atom\app-1.19.0-beta1\resources\app\node_modules\github\lib\async-queue.js:7:105
exports._errnoException @ util.js:1022
ChildProcess.spawn @ internal/child_process.js:313
exports.spawn @ child_process.js:399
exports.execFile @ child_process.js:160
module.(anonymous function) @ ELECTRON_ASAR.js:200
(anonymous) @ C:\Users\conwelps\AppData\Local\atom\app-1.19.0-beta1\resources\app\node_modules\dugite\build\lib\g…:65
exec @ C:\Users\conwelps\AppData\Local\atom\app-1.19.0-beta1\resources\app\node_modules\dugite\build\lib\g…:48
executeGitCommand @ <embedded>:175143
(anonymous) @ <embedded>:175014
step @ <embedded>:174874
(anonymous) @ <embedded>:174874
(anonymous) @ <embedded>:174874
Promise @ <embedded>:175111
(anonymous) @ <embedded>:175012
step @ <embedded>:174874
(anonymous) @ <embedded>:174874
(anonymous) @ <embedded>:174874
(anonymous) @ <embedded>:93858
step @ <embedded>:93839
(anonymous) @ <embedded>:93839
(anonymous) @ <embedded>:93839
execute @ <embedded>:93863
(anonymous) @ <embedded>:93928
step @ <embedded>:93839
(anonymous) @ <embedded>:93839
(anonymous) @ <embedded>:93839
processTask @ <embedded>:93934
processQueue @ <embedded>:93908
push @ <embedded>:93895
exec @ <embedded>:174942
(anonymous) @ <embedded>:175184
step @ <embedded>:174874
(anonymous) @ <embedded>:174874

The logs look basically the same in 1.18.


#2

Looks like some kind of problem running Git commands but not sure what the issue could be - could you go ahead and open an issue in the GitHub package repository so the developers can take a look?


#3

Did you ever get an answer to this? I’ve been getting no where. Each time i try to put in a support ticket somewhere, I get told to go somewhere else. I’ve now come full circle…

Started at github and the rules say to go to a sub forum, then the sub forum tells you to go to the support part, then it points me here… which points me back at laskjf;alskjkladssaldj github…

please tell me you figured this crap out? (yes yes necro bad, but this is pretty much literally where i’m at right now. So it must be the same issue)


#4

What directed you here? Issues with Atom are always accepted on the repo issue list AFAIK.

You may have been redirected to the actual atom/github repo though.


#5

On the github, when i clicked the ‘new issue’ button the following message is the first thing i saw. Since I have no idea if it’s actually a problem with the app, or just me being retarded, I counted it as a question/looking for support.

"
Have you read Atom’s Code of Conduct? By filing an Issue, you are expected to comply with it, including treating everyone with respect: https://github.com/atom/atom/blob/master/CODE_OF_CONDUCT.md

Do you want to ask a question? Are you looking for support? The Atom message board is the best place for getting support: https://discuss.atom.io
"


#6

That is an automated filler message to help newbies find a better place to go for questions and discussion topics. The GitHub issues are for reporting bugs like the one that @ltconwell observed. This is the appropriate place for trying to find out what an unidentified problem is in case a bug report is warranted (in most cases, it’s a PEBKAC issue or one of us can explain or offer a workaround).


#7

Dealing with Atom and more specifically - Packages within Atom - is not always a PICNIC.