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

Failed to open workspace settings file under empty workspace #177639

Closed
yiliang114 opened this issue Mar 20, 2023 · 2 comments
Closed

Failed to open workspace settings file under empty workspace #177639

yiliang114 opened this issue Mar 20, 2023 · 2 comments
Assignees
Labels
author-verification-requested Issues potentially verifiable by issue author bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders verified Verification succeeded vscode.dev Issues related to vscode.dev web Issues related to running VSCode in the web
Milestone

Comments

@yiliang114
Copy link
Contributor

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version:
    • 版本: 1.76.2
    • 提交: ee2b180
    • 日期: 2023-03-14T17:47:26.641Z
    • 浏览器: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/111.0.0.0 Safari/537.36
  • OS Version: Mac os intel

Steps to Reproduce:

  1. Open https://vscode.dev/
  2. Use cmd + , to open Settings
  3. Switch to workspace settings
  4. Click Open Setting(JSON) in the upper right corner

image

image

@VSCodeTriageBot VSCodeTriageBot added the stale Issues that have not been triaged in an appropriate amount of time label Mar 27, 2023
@Tyriar Tyriar assigned joaomoreno and unassigned Tyriar and sandy081 Mar 29, 2023
@VSCodeTriageBot VSCodeTriageBot removed triage-needed stale Issues that have not been triaged in an appropriate amount of time labels Mar 29, 2023
@joaomoreno joaomoreno assigned bpasero and unassigned joaomoreno Apr 18, 2023
@bpasero bpasero added web Issues related to running VSCode in the web vscode.dev Issues related to vscode.dev bug Issue identified by VS Code Team member as probable bug labels Apr 18, 2023
@bpasero bpasero added this to the April 2023 milestone Apr 19, 2023
@bpasero
Copy link
Member

bpasero commented Apr 19, 2023

Good catch, this was an oversight from introducing temporary workspaces. We never actually created the workspace file in-memory. Funny how things did not explode elsewhere.

@VSCodeTriageBot VSCodeTriageBot added unreleased Patch has not yet been released in VS Code Insiders insiders-released Patch has been released in VS Code Insiders and removed unreleased Patch has not yet been released in VS Code Insiders labels Apr 19, 2023
@bpasero bpasero added the author-verification-requested Issues potentially verifiable by issue author label Apr 20, 2023
@VSCodeTriageBot
Copy link
Collaborator

This bug has been fixed in the latest release of VS Code Insiders!

@yiliang114, you can help us out by commenting /verified if things are now working as expected.

If things still don't seem right, please ensure you're on version 208bbb0 of Insiders (today's or later - you can use Help: About in the command palette to check), and leave a comment letting us know what isn't working as expected.

Happy Coding!

@DonJayamanne DonJayamanne added the verified Verification succeeded label Apr 26, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Jun 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
author-verification-requested Issues potentially verifiable by issue author bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders verified Verification succeeded vscode.dev Issues related to vscode.dev web Issues related to running VSCode in the web
Projects
None yet
Development

No branches or pull requests

7 participants