handshake authorized

[Pestov]

Hi! ungit is amazing! But when I switch derictory to my old git projects, ungit show me my gits per second and next "Connection lost" handshake authorized. When I refresh page this loop repeat. I teminal "handshake authorized".

Thanks a lot for your project

[FredrikNoren]

Thanks, and thanks for the report :) Hm I need a little bit more information to debug this, can you try to look in your console in your browser and also the output of ungit in the command line to see if there are any errors there?

[jmparra]

I have the same problem, here the log it generates: ... info: GET /images/shadowArrowRight.png info: GET /images/blueArrowRight.png info: GET /fonts/glyphiconshalflings-regular.woff info: Sending exception to bugsense error: Error: EMFILE, open '/usr/local/lib/node_modules/ungit/public/fonts/glyphiconshalflings-regular.woff' error: TypeError: Cannot read property 'body' of undefined at /usr/local/lib/node_modules/ungit/source/bugsense.js:50:109 at Request.callback (/usr/local/lib/node_modules/ungit/node_modules/superagent/lib/node/index.js:585:30) at ClientRequest. (/usr/local/lib/node_modules/ungit/node_modules/superagent/lib/node/index.js:553:10) at ClientRequest.EventEmitter.emit (events.js:95:17) at Socket.socketErrorListener (http.js:1520:9) at Socket.EventEmitter.emit (events.js:95:17) at net.js:813:16 at process._tickCallback (node.js:415:13) info: Sending exception to bugsense error: TypeError: Cannot read property 'body' of undefined at /usr/local/lib/node_modules/ungit/source/bugsense.js:50:109 at Request.callback (/usr/local/lib/node_modules/ungit/node_modules/superagent/lib/node/index.js:585:30) at ClientRequest. (/usr/local/lib/node_modules/ungit/node_modules/superagent/lib/node/index.js:553:10) at ClientRequest.EventEmitter.emit (events.js:95:17) at Socket.socketErrorListener (http.js:1520:9) at Socket.EventEmitter.emit (events.js:95:17) at net.js:813:16 at process._tickCallback (node.js:415:13) info: Sending exception to bugsense info: GET /fonts/glyphiconshalflings-regular.ttf info: emitting changed to sockets, manually triggered info: GET /api/status?path=%2FUsers%2Fjmparra%2FDocuments%2Fpm%2FOldproject info: GET /api/log?path=%2FUsers%2Fjmparra%2FDocuments%2Fpm%2FOldproject&limit=25 info: GET /api/checkout?path=%2FUsers%2Fjmparra%2FDocuments%2Fpm%2FOldproject info: GET /api/remotes?path=%2FUsers%2Fjmparra%2FDocuments%2Fpm%2FOldproject info: Exception sent to bugsense info: App version: 0.1.6 info: socket.io started info: Listening on port 8866

Ungit started

info: handshake authorized info: handshake authorized

[Leandros]

Same here. Using OS X 10.8

child_process.js:927
    throw errnoException(process._errno, 'spawn');
          ^
Error: spawn EMFILE
    at errnoException (child_process.js:980:11)
    at ChildProcess.spawn (child_process.js:927:11)
    at exports.spawn (child_process.js:715:9)
    at Object.exports.execFile (child_process.js:607:15)
    at Object.exports.exec (child_process.js:578:18)
    at /usr/local/lib/node_modules/ungit/source/git.js:12:31
    at Object.q.process [as _onImmediate] (/usr/local/lib/node_modules/ungit/node_modules/async/lib/async.js:728:21)
    at processImmediate [as _immediateCallback] (timers.js:330:15)
info: socket.io started
info: Listening on port 8448
## Ungit started ##
info: handshake authorized

[erichs]

Brand new install:

nodejs v 0.10.14 npm v 1.3.3 ungit v 0.1.6 git v 1.7.1

cd into pre-existing git directory, and type 'ungit': info: transport end (undefined) info: GET / info: GET /css/styles.css info: GET /config.js info: GET /version.js info: GET /js/bugsense.js info: GET /js/ungit.js info: GET /favicon.ico info: handshake authorized info: GET /api/latestversion info: GET /images/logo.png info: GET /images/repositoryBackgroundArrowUp.png info: GET /images/logoLarge.png info: GET /api/status?path=%2Fhome%2Fersmith%2Frepos%2Fdotfiles info: GET /fonts/OpenSans.woff

[FredrikNoren]

The "handshake authorized" thing is just socket.io saying it's succeded connecting with the ui in the browser.

@jmparra and @Leandros your issue seems to be #118

@erichs Hm that seems like a pretty normal "ok" log, what problem are you experiencing exactly?

[erichs]

I get the following when I browse the URL: Whooops Something went wrong, reload the page to start over.

Is there a way I can turn on debugging or verbosity?

On Mon, Aug 26, 2013 at 5:02 PM, FredrikNoren notifications@github.comwrote:

The "handshake authorized" thing is just socket.io saying it's succeded connecting with the ui in the browser.

@jmparra https://github.com/jmparra and @Leandroshttps://github.com/Leandrosyour issue seems to be

118 https://github.com/FredrikNoren/ungit/issues/118

@erichs https://github.com/erichs Hm that seems like a pretty normal "ok" log, what problem are you experiencing exactly?

— Reply to this email directly or view it on GitHubhttps://github.com/FredrikNoren/ungit/issues/138#issuecomment-23294496 .

[Leandros]

Just look at your console were you started it, there is a log ....

[erichs]

Right... That previous output was the console log. It doesn't appear to offer any helpful errors or diagnostic outputs. Not sure why I'm getting 'Whoops'.

If it helps, I get the same HTML and console output when I launch ungit from within a new repo:

mkdir foo && cd foo git init foo ungit

On Tue, Aug 27, 2013 at 10:08 AM, Arvid Gerstmann notifications@github.comwrote:

Just look at your console were you started it, there is a log ....

— Reply to this email directly or view it on GitHubhttps://github.com/FredrikNoren/ungit/issues/138#issuecomment-23338955 .

[Leandros]

Shouldn't matter from were you start it. Same as navigating to it. I'am interested, which OS?

[erichs]

Red Hat Enterprise Linux Workstation release 6.4 (Santiago)

On Tue, Aug 27, 2013 at 10:22 AM, Arvid Gerstmann notifications@github.comwrote:

Shouldn't matter from were you start it. Same as navigating to it. I'am interested, which OS?

— Reply to this email directly or view it on GitHubhttps://github.com/FredrikNoren/ungit/issues/138#issuecomment-23340029 .

[FredrikNoren]

@erichs Can you look in the browsers console too?

[FredrikNoren]

The original issues seems to have been sorted here, @erichs if you find out what's not working please open a ticket for that. Closing this one.