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
{{ message }}
Repository navigation
Cannot revert to older version if newest one crashes #3632
Other extensions you installed (and if the issue persists after disabling them):
A clear and concise description of what the bug is:
The extension updates itself to the newest release, ignoring vscode's settings regarding updates.
That way, if the newest version crashes for you, all you can do is wait for it to get fixed.
Downgrade the extension ([The cog next to the extension] > Install another version)
Restart vscode
See the extension upgrade to the newest version anyways
Expected behavior
The extension should rely on vscode's update mechanisms.
OR
Allow you to lag at least one version behind somehow, so you're not blocked until an issue is fixed.
Benno Straub (@Cannedfood) You also need to change the C_Cpp.updateChannel to "Default" instead of "Insiders".
Also, we're releasing a fix for a high hitting crash today with 0.23.1. If you're still getting a crash with 0.23.1, we could fix the crash if a call stack can be obtained.
This should be fixed starting with 0.25.1 (as in, we check the extensions.autoUpdate before updating) -- however, if you revert to a version older than 0.25.0, then it won't have that fix so, so the benefit would only start when we release 0.26.0-insiders and you change to 0.25.1.
Activity
pieandcakes commentedon May 13, 2019
Bob Brown (@bobbrow) Sean McManus (@sean-mcmanus) this should be working for Benno Straub (@Cannedfood) right?
sean-mcmanus commentedon May 13, 2019
Benno Straub (@Cannedfood) You also need to change the C_Cpp.updateChannel to "Default" instead of "Insiders".
Also, we're releasing a fix for a high hitting crash today with 0.23.1. If you're still getting a crash with 0.23.1, we could fix the crash if a call stack can be obtained.
bobbrow commentedon May 16, 2019
We should change the behavior and let the vscode setting override ours. We were doing the opposite previously.
sean-mcmanus commentedon Aug 30, 2019
This should be fixed starting with 0.25.1 (as in, we check the extensions.autoUpdate before updating) -- however, if you revert to a version older than 0.25.0, then it won't have that fix so, so the benefit would only start when we release 0.26.0-insiders and you change to 0.25.1.