-
Notifications
You must be signed in to change notification settings - Fork 29.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VSCode should respect the Metered Connection flag on Windows, and not download updates #60741
Comments
(Experimental duplicate detection) |
Thank you @vscodebot, but since #8540 is already closed, I would like to leave this issue open. The only way I can work with VSCode now, while on a metered connection, is by disabling all update-settings. |
Duplicate of #8540 |
Thank you @egamma, please help me understand why this is not considered a bug - I noticed you added the feature label. Thanks! |
I've found this documentation by Microsoft on detecting metered connections from javascript: https://msdn.microsoft.com/en-us/library/hh750310 |
I'm abandoning this idea, various reasons. |
general info
I've only found #27758 to be slightly related, that's more of a feature request, while I consider this to be a bug, where a MS product, on a MS platform does not respect the 'metered connection' setting.
On VSCode Insiders - I've skipped this check, because it makes no sense in the context of this issue.
Version: 1.28.0 (user setup)
Commit: 431ef9d
Date: 2018-10-05T14:58:53.203Z
Electron: 2.0.9
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64
1083 build 17134.285
Steps to Reproduce:
Does this issue occur when all extensions are disabled?: Yes/No
Yes
Actual behaviour
VSCode detects a newer version is avaliable, and starts downloading it, even while on a metered connection.
Expected behaviour
VSCode detects that i'm on a metered connection and only indicates that an update is available, but does not automatically download it.
Remarks
I love VSCode, and I would love it more if it also respected my wallet :-)
Work-around: disable updates by unchecking 'windows background update' and set updates to 'none'.
The text was updated successfully, but these errors were encountered: