-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Color contamination to the console if the program was terminated by Ctrl+C #494
Comments
@yfdyh000 thanks for pointing this out. By the way, you can configure the TTL on the cache refresh with this version of the client in settings. We've been looking at bandwidth issues recently. |
@yfdyh000 is this still happening. We believe this may have been fixed in an earlier release. |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment. |
@yfdyh000 this issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment. |
@yfdyh000 this issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment. |
Color contamination to the console if the program was terminated by Ctrl+C
Steps to reproduce
Run
winget source list update
, orwinget search [name]
(while cache is not ready) in cmd window.While like "/" status, press Ctrl+C hotkey to terminate it, probably due to slowness.
Expected behavior
Reset the character color to normal when the program is terminated.
Actual behavior
The new characters remain blue.
Environment
In China, I see the
winget source update
often takes tens of seconds or minutes to complete. Only thehttps://winget.azureedge.net/cache
configured and it is accessible from browser.The text was updated successfully, but these errors were encountered: