Skip to content

提示c/c++已经更新到0.24.0版本,reload后没有生效 #3800

Closed

Description

@lujfsd

Issue Type: Bug

在WSL中,系统提示"The C/C++ Extension has been updated to version 0.24.0-insiders. Please reload the window for the changes to take effect.",点击reload后,没有生效。会一直提示
1560993752(1)

Extension version: 0.23.1
VS Code version: Code 1.35.1 (c7d83e57cd18f18026a8162d042843bda1bcf21f, 2019-06-12T14:30:02.622Z)
OS version: Windows_NT x64 10.0.17763
Remote OS version: Linux x64 4.4.0-17763-Microsoft

System Info
Item Value
CPUs Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz (8 x 1800)
GPU Status 2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 7.85GB (1.98GB free)
Process Argv
Screen Reader no
VM 67%
Item Value
Remote WSL
OS Linux x64 4.4.0-17763-Microsoft
CPUs Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz (8 x 1800)
Memory (System) 7.85GB (1.98GB free)
VM 67%

Activity

  1. sean-mcmanus commented on Jun 20, 2019

    @sean-mcmanus
    Contributor

    What is your question? You can set the C_Cpp.updateChannel to "Default" to switch back to 0.23.1.

  2. lujfsd commented on Jun 20, 2019

    @lujfsd
    Author

    new version 0.24.0 is not effect after reload.

  3. sean-mcmanus commented on Jun 20, 2019

    @sean-mcmanus
    Contributor

    Do you mean the pop up keeps re-appearing? If you can check the extensions folder to see if the 0.23.1 and/or 0.24.0-insiders folder are still there that would help.

  4. lujfsd commented on Jun 20, 2019

    @lujfsd
    Author

    yes. it's re-appear.my extensions folder as below:
    1560997003(1)
    just 0.23.1

  5. sean-mcmanus commented on Jun 20, 2019

    @sean-mcmanus
    Contributor

    Okay, it looks like the download/install is failing for some unexpected reason and we don't handle the error well. Until we're able to figure out a fix, your best option is to change the updateChannel setting. The code that is causing this failure is open source if you feel like debugging it yourself with our release branch, but you'd have to change the "testingInsidersVsixInstall" variable to "true" in githubAPI.ts.

  6. added
    investigate: reproThis issue's repro steps needs to be investigated/confirmed
    and removed
    more info neededThe issue report is not actionable in its current state
    on Jun 20, 2019
  7. lujfsd commented on Jun 20, 2019

    @lujfsd
    Author

    OK,Thanks

  8. added
    fixedCheck the Milestone for the release in which the fix is or will be available.
    on Dec 19, 2019
  9. sean-mcmanus commented on Jan 22, 2020

    @sean-mcmanus
    Contributor
  10. locked and limited conversation to collaborators on Oct 8, 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.help wantedCan be fixed in the public (open source) repo.insidersCurrently only repros with our latest Insiders release.investigate: reproThis issue's repro steps needs to be investigated/confirmed

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions