microsoft / microsoft/vscode-remote-release
vscode.workspace.requestWorkspaceTrust() asks for trust for trusted canonical URI and hangs
@sbatten is already working on this.
Since Oct 26, 2023.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Blocks: https://github.com/microsoft/vscode-remote-release/issues/9139
I'm trying to fix the canonical URI for the dev container to be equal to the Remote-SSH URI for the folder, but when I have that fixed vscode.workspace.requestWorkspaceTrust still triggers a trust dialog and doesn't return after I click Trust in the UI.
The dev container URI is: vscode-remote://dev-container%2B7b22686f737450617468223a22633a5c5c55736572735c5c6368726d617274695c5c646576656c5c5c736d6b747374222c226c6f63616c446f636b6572223a66616c73652c22636f6e66696746696c65223a7b22246d6964223a312c2270617468223a222f633a2f55736572732f6368726d617274692f646576656c2f736d6b7473742f2e646576636f6e7461696e65722f646576636f6e7461696e65722e6a736f6e222c22736368656d65223a227673636f64652d66696c65486f7374227d7d@ssh-remote%2Bwin11-server2/workspaces/smktst
The canonical URI is: vscode-remote://ssh-remote%2Bwin11-server2/c%3A/Users/chrmarti/devel/smktst
The UI stays in a "in progress" state indefinitely:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.