Hyper: Constant "Error fetching updates" notifications

Created on 18 Jul 2016 · 15Comments · Source: vercel/hyper

Each time hyperterm fails to check for updates, it creates a system notification ("Error fetching updates"). It seems that hyperterm checks every 10-15 minutes or so, leading to the annoyance of many new system notifications.

In my case, it's likely due to the necessary ports being blocked at work, but there could be a number of other reasons why hyperterm might not be able to check for updates. Would it be better to have hyperterm fail silently when checking for updates?

Edit: Some sort of exponential backoff could be good for this, as well.

Bug In Progress

Source

sethlopezme

👍13

Most helpful comment

Getting a similar error...

jcreamer898 on 26 Jul 2016

👍2

All 15 comments

Or stop checking for updates after X failed attempts :)

montogeek on 18 Jul 2016

I'm getting this as well. Looks like the autoupdater feed URL uses a .sh top-level domain. That is likely to be blocked in many work environments. Would it be possible to switch to a more common TLD?

ahutchings on 19 Jul 2016

👍2

Here's a screenshot of the error. If someone can direct me to the location of a log file, or something else that would help in debugging this, I'd be happy to help.

screen shot

alanhussey on 20 Jul 2016

I'm also having this issue

rwwagner90 on 25 Jul 2016

I've got the same issue. It varies between "the request timed out," "the network connection was lost," and something like "could not locate bundle" (I didn't catch the exact message)

controversial on 26 Jul 2016

Getting a similar error...

jcreamer898 on 26 Jul 2016

👍2

@jcreamer898 That's the one I've got (or, rather, one of the three). Any idea what causes this @rauchg ? The developer console doesn't have any information besides a lot of repeated Cannot read property 'shell' of undefined errors

controversial on 26 Jul 2016

Possibly have them hosted on github (when signing works)?

albinekb on 26 Jul 2016

This should be resolved shortly. We switched to a new builder mechanism that introduced a minor mismatch

rauchg on 26 Jul 2016

👍1

I have gotten a lot of different error messages. I think this screenshot includes them all. I received notifications for all of these (and more) within the past hour.