Skip to content
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

Cache Editor UI Button SAVE don't save to file #2795

Closed
mariuszmaximus opened this issue Oct 14, 2022 · 2 comments
Closed

Cache Editor UI Button SAVE don't save to file #2795

mariuszmaximus opened this issue Oct 14, 2022 · 2 comments
Assignees
Labels
bug a bug in the product investigation needed issues needs a developer assigned to it and investigation done in order to implement a fix
Milestone

Comments

@mariuszmaximus
Copy link

mariuszmaximus commented Oct 14, 2022

Brief Issue Summary

  1. git clone https://github.com/DCMTK/dcmtk.git
  2. open dcmtk in vscode
  3. click on bottom bar "CMake: [Debug]"
  4. open "CMake Cache Editor" [UI]
  5. find "DCMTK_MODULES" and clear value
  6. press Button SAVE

At this point we can't save any string value in "Cache Editor UI"

I tested Windows 10/11 and Linux Ubuntu last 22.04 LTS

tested on last Release: v1.12.27
and Pre-Release: v1.13.13

CMake Tools Diagnostics

No response

Debug Log

No response

Additional Information

No response

@elahehrashedi elahehrashedi added this to the On Deck milestone Oct 14, 2022
@bobbrow bobbrow added bug a bug in the product investigate labels Oct 14, 2022
@elahehrashedi
Copy link
Contributor

Thank you for submitting this issue. We will investigate it.

@gcampbell-msft gcampbell-msft added investigation needed issues needs a developer assigned to it and investigation done in order to implement a fix and removed investigate labels Oct 4, 2023
@github-project-automation github-project-automation bot moved this to Triage Needed in CMake Tools Nov 29, 2023
@gcampbell-msft gcampbell-msft moved this from Triage Needed to Pending Prioritization in CMake Tools Nov 29, 2023
@gcampbell-msft gcampbell-msft modified the milestones: On Deck, 1.17 Dec 12, 2023
@gcampbell-msft gcampbell-msft moved this from Pending Prioritization to Ready to be Assigned in CMake Tools Dec 12, 2023
@gcampbell-msft gcampbell-msft self-assigned this Dec 20, 2023
@gcampbell-msft gcampbell-msft moved this from Ready to be Assigned to To Do in CMake Tools Dec 20, 2023
@gcampbell-msft gcampbell-msft moved this from To Do to In Progress in CMake Tools Dec 20, 2023
@gcampbell-msft gcampbell-msft moved this from In Progress to Completed in CMake Tools Jan 3, 2024
@boxerab
Copy link

boxerab commented Nov 21, 2024

I am having this same issue on Fedora 41 with vscodium

Version: 1.95.3
Release: 24321
Commit: dc5a551c256719475d2d0959270e3836c9bbb632
Date: 2024-11-16T01:21:03.577Z
Electron: 32.2.5
ElectronBuildId: undefined
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Linux x64 6.11.8-300.fc41.x86_64

Here are steps to repro:

  1. open vscodium
  2. edit cmake cache using text editor OR UI
  3. change build type to release
  4. save
  5. exit vscodium
  6. reopen
  7. edit cmake cache using text editor OR UI
  8. build type has now been set back to debug

This happens even when editing the cache text file, so it does not seem to be a UI issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug a bug in the product investigation needed issues needs a developer assigned to it and investigation done in order to implement a fix
Projects
Status: Completed
Development

No branches or pull requests

5 participants