Automatic Update

parkd1 · August 20, 2015, 09:59:26 AM

Not sure if this a bug or something wrong with my computer. I get the this error when I do Automatic Update and let it update.

parkd1 · August 20, 2015, 10:06:17 AM

When I got the error it told me to get the whole installer. When I went to get it I get this error.

Not Found

The requested URL /support/temp/20316_x64_8.7.0.1 beta.zip was not found on this server.

Thanks.

Jeremy Collake · August 20, 2015, 10:33:06 AM

Thanks park1d.

The auto-update error I *think* is most likely due to a broken download - though I'm checking to make sure it wasn't a broken package (uploads are verified).

The Support area missing beta download I'll also be fixing in minutes.

parkd1 · August 20, 2015, 10:36:25 AM

Welcome.

Jeremy Collake · August 20, 2015, 10:39:38 AM

Support area download fixed (usual naming issue we've seen before).

Automated update archives all look like they were transferred correctly to the server, so I'm still inclined to think it was a broken download, *but* I am going to publish v8.7.0.3 beta, which will replace them.

parkd1 · August 20, 2015, 10:42:05 AM

Sounds good. Thanks

BenYeeHua · August 20, 2015, 04:52:32 PM

So, maybe adding some SHA1 checking for update?

Then when it is broken because of a broken internet, it will ask the user, or retry itself a few times.

Of cause it may do nothing, as it is already reported by WinRAR, so it should be better to focus on other feature.

---
And yup, it is the end of the archive is broken, so it can be some unexpected disconnection, while it think the file are downloaded completely?

---Off-Topic
And ya, I always having some broken download(loaded the emotion for the background image for the page etc), when I open a lot of pages.
But I guess it is just a browser issues, or a server config issues that can't handle too many connections.

Jeremy Collake · August 20, 2015, 10:30:32 PM

I could do some sort of post-download verification, that's not a bad idea at all. It adds a little complexity, but not much. I'd just need to find the time to implement it. Good idea BenYeeHua!

parkd1 · August 21, 2015, 12:08:27 AM

I second that. Good idea.

Jeremy Collake · August 21, 2015, 12:56:30 PM

It'll be a bit before I get it in, but I'll work on it as part of the new shared (multi-app) code base I'm building. It's really not that hard, I'll just download a list of file hashes first, then check the file against that list.

BenYeeHua · August 21, 2015, 04:49:08 PM

So I guess all update connection already running on HTTPS?

Hotrod · September 15, 2016, 05:38:56 PM

I'm running 8.9.8.44 and my updater is refusing to get the new 8.9.8.48 on 3 W10 machines and 2 XP machines.

edkiefer · September 15, 2016, 05:54:56 PM

8.9.8.48 was just released min ago, give it some time.
I am on .47 and not seeing as of this min.

Edit: Try now should work.

Jeremy Collake · September 15, 2016, 06:20:18 PM

Sorry, the build took a while, sometimes network congestion causes digital signing time-stamping problems. It's finally out now, new final version.

Hotrod · September 16, 2016, 01:29:03 AM

I had to run some errands, got it around 5pm. It's all good.

I just wanted JC to know as early as possible if there really was an issue.

BenYeeHua · September 16, 2016, 04:19:38 PM

Ya, it is good thing, thank for doing that.

Jeremy Collake · September 19, 2016, 12:18:17 AM

FWIW, the temporarily seen (for a couple minutes) 'old version' update anomalies are a side-effect of CloudFlare's caching, I have to selectively or wholly clear the cache after every update, and the timing has to be just right, etc... CloudFlare edge nodes serve 75% of our bandwidth throughout the world, so the service itself has been very beneficial, if also adding a bit more complexity to the site ecosystem.