Check for update not detecting new version

[Matt]

Currently running Everything Version 1.4.1.877 (x64), Windows 10 Pro.

Clicking on Help -> Check for Updates... results in "Everything is up to date!", but on the voidtools homepage, the latest version is 1.4.1.924.

Looking at the verbose debug log file I can see these entries:

Code: Select all

2019-01-07 11:05:05.118: update: connecting to www.voidtools.com...
...
Some log entries to do with GetVolumeNameForVolumeMountPoint 
...
2019-01-07 11:05:05.297: update: available version: 1.4.1.877

So it can see an update is available but nothing seems to happen.

[NotNull]

When checking for updates, Everything will check against http://www.voidtools.com/everything/update.ini ( http://www.voidtools.com/everything/beta-update.ini for the "beta-channel" ).

Currently: 1.4.1.877 (1.4.1.895 for the "beta-channel"), so in that sense you are seeing the right version (you are running 1.4.1.877, which equals to the version in update.ini)

However, there are newer versions available (most recent:1.4.1.926). Those can be downloaded from the Beta Nightly Builds

@void has his own criteria for 'promoting/publishing' versions. That's why you don't see those newer versions when checking for updates.

HTH ...


BTW:
- you can switch to the beta-channel in Everything.ini: beta_updates=1
- Seee also: https://www.voidtools.com/update/

[Matt]

Ahh I missed the /Update page. Thanks!

[void]

I have not pushed out notifications for the "newer" versions yet as the changes are very minor and in some cases causing issues for some users.

1.4.1.926 is currently the most stable release.

[tuska]

If a final version (Public release) is offered for download on this pages:
https://www.voidtools.com/
https://www.voidtools.com/downloads/
then I think an adjustment should be made [even if few users may have a problem with it].

Btw, "About Everything... CTRL+F1" --> still shows http://www.voidtools.com/ (without "s").
Perhaps an adjustment could also be made here.

Please check.
Thank you!
______________________________________________________________________________
Windows 10 Pro (x64) Version 1809 (OS Build 17763.253)
Intel(R) Core(TM) i7-4770 CPU @ 3.4OGHz, 16 GB RAM
Everything - Version 1.4.1.928 (x64) - Public release
Everything - Version 1.4.1.928 (x64) - Beta Nightly Builds

[void]

Btw, "About Everything... CTRL+F1" --> still shows http://www.voidtools.com/ (without "s").

Updated to https:// for the next major version.

Thanks.

[tuska]

2David
To be honest, I don't quite understand the current publishing policy.

If I personally would use the version 1.4.1.877, then I would be surely interested also at further "Public releases",
especially if they have already been announced on the homepage.

update.ini

Code: Select all

major=1
minor=4
revision=1
build=877  (!)

beta-update.ini

Code: Select all

major=1
minor=4
revision=1
build=895

If I remember correctly, version 1.4.1.895 was offered for download on the homepage for a long time (-> update.ini: .877 !?).

Code: Select all

[928] Public release  11.‎01.‎2019 ‏‎17:09
[927] Public release
[924] Public release.
[922] Public release.
[895] Public release. 09.‎02.‎2018 ‏‎14:41
[877] Official 1.4 stable release.    07.‎06.‎2017 ‏‎12:12

viewtopic.php?p=24519#p24519 1.4.1.926 is currently the most stable release.

Currently also the entry

Code: Select all

beta_updates=1

in the Everything.ini has no effect.

I did not check the parameter check_for_updates_on_startup=1.
However, a user in another forum meant that "Check for Updates..." would display the following:
"With existing version 1.4.1.895 the message appears after pressing the "Check for Updates..." button: You are using the current version.
Now manually on version 1.4.1.928 the same note appears."
Hmmm.

So there's nothing left for interested users to do at the moment but to regularly visit the Everything 1.4.1 Beta Nightly Builds website
to check if there are newer and more stable versions. [Should a version "not fit", one can download a previous version from this page].

[NotNull]

Code: Select all

beta_updates=1

in the Everything.ini has no effect.

I did not check the parameter check_for_updates_on_startup=1.
However, a user in another forum meant that "Check for Updates..." would display the following:
"With existing version 1.4.1.895 the message appears after pressing the "Check for Updates..." button: You are using the current version.
Now manually on version 1.4.1.928 the same note appears."
Hmmm.

And that's exactly how it should work! (if I understand correctly)
When you are running version 895 and configured beta_updates=1 (newest offered is 895), you are running the most recent version, compared to the 895 version that is offered in the beta-ini.

Tested it myself: installed 877, did a Menu:Help > Check for Updates and got:

2019-01-21 17_49_16-Everything.png (13.45 KiB) Viewed 27035 times

BTW: I came here through a thread in the (German section of) Total Commander forum (link)
Quite a few familiar names on that forum

[tuska]

And that's exactly how it should work! (if I understand correctly)
When you are running version 895 and configured beta_updates=1 (newest offered is 895), you are running the most recent version, compared to the 895 version that is offered in the beta-ini.

Your example with version 877 -> 895 is of course OK.

But in my opinion there is the problem that
- when using version 895 with query for program update(s) already 5(!) more current versions (Public releases) were announced
- at least the last version 928 has already been offered for download on the website
- when using version 895, the message "You are using the current version of "Everything" still appears today

Email of January 16, 2019 from David C. (on the occasion of an email correspondence and feedback of test results from me)
"Once the bug reports for the current version die down I'll update the notifications".

BTW: I came here through a thread in the (German section of) Total Commander forum (link)
Quite a few familiar names on that forum

[NotNull]

Ah, miscommunication ...

I thought it was about about the mechanism not functioning properly and you are talking about updating the update.ini files ..

You can ignore my message, then.

EDIT:
Beside the reasons already mentioned by @void for not updating the update.ini's (just minor changes; can cause issues), I guess bandwidth might be an issue too.
If you look at the numbers that are downloaded just through Softpedia alone (version 1.4.1.928 has been downloaded over 50.000 times!) That is ... substantial.

(Link: https://win.softpedia.com/dyn-search.ph ... everything)

[tuska]

EDIT:
Beside the reasons already mentioned by @void for not updating the update.ini's (just minor changes; can cause issues), I guess bandwidth might be an issue too.
If you look at the numbers that are downloaded just through Softpedia alone (version 1.4.1.928 has been downloaded over 50.000 times!) That is ... substantial.

Yes, it may all be so.

Personally, I don't like that I can set an option that has no effect, or
that I can make queries for program updates that give me false information.

I am not affected in principle, because I have been downloading the latest Beta Nightly builds for a long time.

Since there were already questions in this forum as well as in the Total Commander forum, I tried here,
to assist the thread starter with this issue.

[NotNull]

Personally, I don't like that I can set an option that has no effect, or
that I can make queries for program updates that give me false information.

I am not affected in principle, because I have been downloading the latest Beta Nightly builds for a long time.

Since there were already questions in this forum as well as in the Total Commander forum, I tried here,
to assist the thread starter with this issue.

Agreed. (That could have been my text ) Especially that the public version on the download page is newer than the one in update.ini. That doesn't match in my brain.

But in the end, that's all up to @void.

[defza]

I also get confused when it says no Updates, then I go to the site and version currently downloadable is newer than the one I'm running.
So, I guess the Check for Updates... function isn't entirely the truth.
Then why not report in the "no updates" dialog that there are updates "XYZ version in beta is available", etc etc

[void]

Some of my reasoning for the slow update notifications:

There's not many changes from 1.4.1.935 to Everything 1.4.1.969.
I would like to avoid jamming update notifications down your throat.
Updates can cause more issues than they fix.
The update notifications was originally designed for major, minor and revision changes (not new builds).
voidtools.com has limited bandwidth
I have limited access to different testing environments/hardware (I only test on VMs), so in a sense 969 is beta and new downloads are testing it.

I will periodically update the update information.

Use the beta update channel for more change notifications:

• In Everything, type in the following search and press ENTER:
  /beta_updates=1

nightly builds:
https://www.voidtools.com/forum/viewtopic.php?t=5718

Thoughts and plans:
Everything needs a new update system to make this more seamless..
Proxy support is on my TODO list.
Use the windows store.
Increase voidtools bandwidth.
Add support for Windows Package Manager

[Biff]

Sorry, no notification e-mails anymore.

Thank you for testing, tuska. OK, so updating appears to be not that easy for me, yes, I better will check the website regularly for updates or just wait for the important updates.

Here you can read more about the reasons why.

Yes, very good reasons / idea, too many updates are (if be done manually only) are annoying, indeed.