Errors when working offline

[jpschewe]

Today I was doing some work without being connected to the internet and ungit kept giving me errors. It seems that it doesn't like not being able to talk to the upstream repository.

2017-12-10T18:16:54.754Z - warn: Responding with ERROR:  {"isGitError":true,"errorCode":"offline","command":"-c color.ui=false -c core.quotepath=false -c core.pager=cat -c credential.helper=/home/jpschewe/src/mungit/bin/credentials-helper 2 8448 fetch origin --prune","workingDirectory":"/home/jpschewe/projects/fll-sw/working-dir","error":"ssh: Could not resolve hostname github.com: Name or service not known\r\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists.\n","message":"ssh: Could not resolve hostname github.com: Name or service not known\r","stderr":"ssh: Could not resolve hostname github.com: Name or service not known\r\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists.\n","stdout":""}
2017-12-10T18:16:54.754Z - warn: Sending exception to Sentry.io
raven@2.2.1 alert: failed to send exception to sentry: getaddrinfo ENOTFOUND sentry.io sentry.io:443
raven@2.2.1 alert: failed to send exception to sentry: getaddrinfo ENOTFOUND sentry.io sentry.io:443

Originally posted to mungit at exsilium#9

[jung-kim]

To me, ungit's goal is to "git made easy". To me, this means it does a lot of things in the background automatically for you or bundles some of frequent the operations. And this result us in some what more frequent querying of the remote repos, and communication and failure of those calls will trigger this issue. (Although this particular one is about sentry.io, which is stat tracking api but I'm sure you will face other errors once remove sentry.io)

long time ago I've tried to do some what more offline tolerating version but had some odd same origin policy. I will try to resume this effort again

[jpschewe]

I think it's great that ungit does these things in the background. However I works expect it to fail gracefully and not being up an error reporting screen when this particular issue comes up.

[jpschewe]

It seems that this problem is back. I'm getting a block at the top of my screen "Unhandled git error!" every couple of minutes and it keeps stacking more and more up until I close the browser window or connect to the network with the git server. I then need to close each one individually or reload the page for them all to go away.

[jung-kim]

Hmm, code for this shouldn't have changed. Been crazy busy and will be crazy busy for awhile but will check it when I get a some time.

[oupala]

I'm still having the same problem when using ungit without network or with a non-cooperative proxy (that blocks ssh, and hence git+ssh).

Could there be a flag at startup, such as --no-network, so that all network operated git operation are disabled (git fetch, git push...)?