[ACK] BUG: Set Update Channel Broken?
I tried to change my update channel to make sure I don't get surprised with an update (actually, I shouldn't since I have downloads turned off... but anyways). When I typed the command set update channel to default, nothing visible happened. Also, I have either forgotten where to check for the channel I am on, or it isnt being shown.
Comments
-
The channel is shown in the About box, under the version. Logs indicate setting the channel succeeded normally:
05/18/2015 18:00:30 | INFO | 1 | AppCommand | (1ms) Executing command: SetPreference|Name=UpdateChannel|Value=Default
05/18/2015 18:00:33 | INFO | 1 | UpdatePipelineManager | Starting update check.
05/18/2015 18:00:33 | INFO | 384 | UpdateManager | Immediate check for updates requested.
05/18/2015 18:00:33 | INFO | 384 | UpdateManager | Starting Update Manager processing in 00:00:00.
05/18/2015 18:00:33 | INFO | 384 | UpdateManagerCallback | Checking for updates from 'https://clientservices.logos.com/update/v1/feed/logos6-mac/stable.xml'.
05/18/2015 18:00:37 | INFO | 387 | UpdateManagerCallback | Checking feed for application updates new than version 6.3.0.380 -
Randy W. Sims said:
The channel is shown in the About box, under the version
Nope. Not on Mac.
Randy W. Sims said:Logs indicate setting the channel succeeded normally
Thanks. [Y]
0 -
alabama24 said:
Nope. Not on Mac.
The version (and update channel) is not shown in the part of the screenshot you cropped out; try looking further down (on the left).
0 -
The version (and update channel) is not shown in the part of the screenshot you cropped out; try looking further down (on the left).
No Joy:
0 -
0
-
Randy W. Sims said:
I think it only shows if you have it set to stable or beta, not if it's set to default
Confirmed. I think that is a bug or a deficiency. Also, didn't previous versions provide some sort of feedback that the channel had changed? (Yes, it showed that it was searching for updates).
Also Also (too tired to think of something else): I can't ever remember what the difference is between default and stable. My intent was to move to "stable," but "default" was the auto populated choice given.
0 -
alabama24 said:Randy W. Sims said:
I think it only shows if you have it set to stable or beta, not if it's set to default
Confirmed. I think that is a bug or a deficiency.
That hasn't changed since Logos 4.
alabama24 said:Also, didn't previous versions provide some sort of feedback that the channel had changed? (Yes, it showed that it was searching for updates).
That's the bug and it also occurs in Windows. The log shows internal activity but there is no visible notification
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
That hasn't changed since Logos 4.
I remember now... and it is a deficiency. There isn't a good reason NOT to put it there.
0 -
alabama24 said:Randy W. Sims said:
I think it only shows if you have it set to stable or beta, not if it's set to default
Confirmed. I think that is a bug or a deficiency.
Agreed!
alabama24 said:I can't ever remember what the difference is between default and stable.
If you go to default after beta 1, you will continue to receive beta updates until it goes stable. If you go to stable, you will stay on beta 1 until it goes stable. Or at least that's how I recall it.
I guess that's why the message doesn't say anything for default: it could mean either channel. But it could say 'default (beta)' / 'default (stable)'.
Mac Pro (late 2013) OS 12.6.2
0 -
-
fgh said:
If you go to default after beta 1, you will continue to receive beta updates until it goes stable. If you go to stable, you will stay on beta 1 until it goes stable. Or at least that's how I recall it.
1. 'Default' after Beta 1 means you will continue to receive updates on beta channel until it goes to an RC and then you won't receive another update until it goes Gold i.e. is available on stable channel. So you won't get RC2, RC3, etc. if released only on beta channel.
2. 'Default' after RC1 means you only receive updates on the 'Stable' channel.
3. So 'Default' means either channel and an RC will switch updates from Beta to Stable channel.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:alabama24 said:
Also, didn't previous versions provide some sort of feedback that the channel had changed? (Yes, it showed that it was searching for updates).
That's the bug and it also occurs in Windows. The log shows internal activity but there is no visible notification
Faithlife, this is a definite bug/regression.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:Dave Hooton said:alabama24 said:
Also, didn't previous versions provide some sort of feedback that the channel had changed? (Yes, it showed that it was searching for updates).
That's the bug and it also occurs in Windows. The log shows internal activity but there is no visible notification
Faithlife, this is a definite bug/regression.
I believe this is an effect of our changes to the update process to be less intrusive. If there is an update to be downloaded, you should see a change in the notification icon (the blue numbered circle) in the top right. AFAIK the only time there should be no notification is if there's nothing to download.
I'll check with the developers to see if this is a case where we want to indicate activity, so the user gets tangible feedback that the command has been recognized.
0 -
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
any progress, Dylan?
Not yet, unfortunately. We have a case in, and it's set to be worked on, but no other progress yet.
0 -
Dylan Rondeau said:Dave Hooton said:
any progress, Dylan?
Not yet, unfortunately. We have a case in, and it's set to be worked on, but no other progress yet.
This is fixed in 6.8.
0