Skip to content

Conversation

@jeanp413
Copy link
Contributor

Fixes #249823

@jeanp413
Copy link
Contributor Author

cc @meganrogge as it's terminal related 🙂

@bpasero bpasero assigned meganrogge and unassigned bhavyaus May 27, 2025
@bpasero
Copy link
Member

bpasero commented May 27, 2025

I wonder how the one property can be different from the other 🤔

@jeanp413
Copy link
Contributor Author

Good point, currently remoteAuthority is empty for the web worker extension host context

@jeanp413
Copy link
Contributor Author

Seems that's intended for both webworker extension host and local extension host


@bpasero
Copy link
Member

bpasero commented May 28, 2025

We have a bit more uses of IExtHostContext.remoteAuthority in the workbench and I wonder if these are all disfunct and should be using the environment service, do you want to adopt the others too?

@jeanp413
Copy link
Contributor Author

jeanp413 commented May 28, 2025

I see some usage in MainThreadMcp.ts but I think it's fine in that case as it's related where mpc servers are executed

@Tyriar Tyriar modified the milestones: June 2025, May 2025 Jun 2, 2025
@Tyriar Tyriar enabled auto-merge June 2, 2025 20:04
@Tyriar Tyriar merged commit 1e6e3fe into microsoft:main Jun 2, 2025
7 checks passed
@vs-code-engineering vs-code-engineering bot locked and limited conversation to collaborators Jul 17, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

vscode.env.onDidChangeShell not firing in the webworker extension host

5 participants