You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been noticing this lately around autoupdate settings -- I change a channel or pinned version, or request an immediate update, but launcher doesn't pull the change in a timely fashion. Currently, I've been waiting over 15 minutes for these changes to get picked up by launcher -- I set my update channel to a variety of options, but I see in the logs and kv.sqlite that the channel is still stable. I clicked the MBA to accelerate the control request interval to 5s, so I should see config changes much more quickly than I do.
I haven't done any investigation into this, so I don't know if this issue is limited to only the subsystems I've mentioned, or if it applies to all. It is also possible, though I think unlikely, that the issue is on the control server side instead.
The text was updated successfully, but these errors were encountered:
It's possible, but each time I've encountered this I've made repeated control server data changes within the window (e.g. override update channel, wait a couple minutes, pin a version, wait a few minutes, request an immediate autoupdate, wait a few minutes). So if the effect isn't happening, it isn't happening across multiple sets of subsystem changes.
I've been noticing this lately around autoupdate settings -- I change a channel or pinned version, or request an immediate update, but launcher doesn't pull the change in a timely fashion. Currently, I've been waiting over 15 minutes for these changes to get picked up by launcher -- I set my update channel to a variety of options, but I see in the logs and kv.sqlite that the channel is still
stable
. I clicked the MBA to accelerate the control request interval to 5s, so I should see config changes much more quickly than I do.I haven't done any investigation into this, so I don't know if this issue is limited to only the subsystems I've mentioned, or if it applies to all. It is also possible, though I think unlikely, that the issue is on the control server side instead.
The text was updated successfully, but these errors were encountered: