Skip to content

Conversation

@Datata1
Copy link
Collaborator

@Datata1 Datata1 commented Nov 24, 2024

No description provided.

Simon-Count and others added 30 commits May 16, 2024 08:43
Update download link from preview
Update changelog, description and support
Adding missing compile step to ci script
persistent ci and treeviewtest
Datata1 and others added 28 commits June 10, 2024 12:17
testing no activation events
…This is mandatory, because when off-when-unused workspaces shut down, then the local vscode client cannot initiate properly and we cannot control vscode before the tunnel connection is up. This is a rather sad solution because in THEORY we could control the behavior before vscode's tries to open the tunnel connection, but this API is since 2019 proposal API and it very unlikly that microsoft will change it. Only microsoft extensions are allowed to use proposed API in production vscode and if we want to use such proposed API we need vscode insiders. No casual user has vscode insiders installed. This is the most simple solution to that problem but i dont like that we interfere with global user settings. Why does microsoft allow to change global user settings? I could create an extension and destroy all the user settings of anyone who install my extension. Why is that even possible?!
@Datata1 Datata1 merged commit 018314a into main Nov 24, 2024
0 of 2 checks passed
@Datata1 Datata1 deleted the merge-branch branch November 24, 2024 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants