Skip to content

Cannot revert to older version if newest one crashes #3632

Closed

Description

Type: General

Describe the bug

  • OS and Version: N/A - Platform independent
  • VS Code Version: 1.33.1
  • C/C++ Extension Version: <= 0.23.0
  • 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.

To Reproduce
Steps to reproduce the behavior:

  1. Go to settings
  2. Disable automatic extension updates (Features > Extension Viewlet > Auto Update)
  3. Downgrade the extension ([The cog next to the extension] > Install another version)
  4. Restart vscode
  5. 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.

Activity

  1. pieandcakes commented on May 13, 2019

    @pieandcakes
    Contributor
  2. sean-mcmanus commented on May 13, 2019

    @sean-mcmanus
    Contributor

    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.

  3. bobbrow commented on May 16, 2019

    @bobbrow
    Contributor

    We should change the behavior and let the vscode setting override ours. We were doing the opposite previously.

  4. added this to the June 2019 milestone on May 16, 2019
  5. added
    fixedCheck the Milestone for the release in which the fix is or will be available.
    on Aug 27, 2019
  6. sean-mcmanus commented on Aug 30, 2019

    @sean-mcmanus
    Contributor

    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.

  7. locked and limited conversation to collaborators on Oct 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Language ServicebugfixedCheck the Milestone for the release in which the fix is or will be available.quick fix

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions