Investigation: do not restart Extension host when first folder changes
See original GitHub issueToday we restart the extension host whenever the first folder changes because workspace.rootPath
is always set to that first folder and it never used to change after the extension host started once.
If we would not restart the extension host anymore an extension:
- could use
workspace.rootPath
as before, it would still point to the first folder always (which can beundefined
if the workspace contains no folders) - could subscribe to the
onDidChangeWorkspaceFolders
event to get notified about updates - would see the value of
workspace.rootPath
changing during runtime whenever the first folder changes
Issue Analytics
- State:
- Created 5 years ago
- Reactions:12
- Comments:61 (54 by maintainers)
Top Results From Across the Web
Error : Extension host terminated unexpectedly in VS Code
The solution for the problem : Open your vscode and launch the command palette by ctrl + shift + p enter image description...
Read more >Troubleshoot self-service password reset writeback- Azure ...
Learn how to troubleshoot common problems and resolution steps for self-service password reset writeback in Azure Active Directory.
Read more >Advanced Visual Studio Code for Python Developers
You can use VS Code as a lightweight code editor to make quick changes, ... If no results come up, make sure you...
Read more >windows - hosts file ignored, how to troubleshoot? - Server Fault
It should have no extension ( hosts not hosts.txt ) - be careful if you have configured ... and change the first DNS...
Read more >GitLab Workflow extension for VS Code
Create an issue if there's something you don't like about this feature. Propose functionality by submitting a feature request. Join First Look to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
For the task improvement, I’ve opened https://github.com/microsoft/vscode/issues/90015. Let’s continue further tasks discussion there so we don’t derail the original issue.
Sorry, for the interrupt, a few cents from @PlatformIO => https://marketplace.visualstudio.com/items?itemName=platformio.platformio-ide
2019 was the worse year for VSCode. I’m personally fully disappointed. We spent a ton of effort just to working on workarounds in our extension. Almost every new release brought new problems for us. The 2017-2018 - were super progressive years. New APIs, quick bug fixing, amazing communication with extension providers.
Do you monitor social channels? Do you see what developers now think about VSCode? Do you remember a time when each of us waits for a new VSCode release to see new features and improvements? What do we have today? I pray each day before VSCode’s new release in case it will no bring more problems for us.
Who do need new icons? “cursor”, “highlights”? https://code.visualstudio.com/updates/v1_41 ? What is it? A ton of blocker issues and we work on new hotkeys? Did Microsoft change PMs for VSCode? It looks like YES!
How many years do we need to instruct VSCode understanding Copy/Paste for macOS? https://github.com/platformio/platformio-vscode-ide/issues/606 . Just take a look at @mjbvz twitter account. Every week a new tweet about useless hotkeys… People have been asking for 1 year!!! please fix. No!
Next surprise with the latest update. Instead of thinking about the developer’s workflow, VSCode thinks about machine performance. It asks developers to fully disable a task provider. How??? This is THE KEY component which drives the whole of our extension. See tons of public complaints https://community.platformio.org/t/pio-vsc-cant-build-no-tasks-found/10488 . You can’t imagine how many similar letters we receive in private support.
Yes, our task provider depends on reading
platformio.ini
file from the user machine and provides dynamic tasks. This is a super-fast operation and is fully asynchronous https://github.com/platformio/platformio-vscode-ide/blob/develop/src/tasks.js#L41a) I know, this is an open-source and everyone can contribute. But! This is not a typical open source project. This is a strategic project by @Microsoft. The “open source” just only a screen before the further strategic business model.
b) Our extension is the most rated extension in the WHOLE marketplace. You can not imagine what is the price of these efforts. Do you know what we receive for promoting VSCode to a hundred thousand developers? NOTHING! We even don’t have minimal support where someone could help with fixing critical and blocker issues. I’ve never seen so high pride. I agree we are NOTHING in comparison with Microsoft. But you don’t understand one thing… If you want to create the best editor for everyone, you MUST TALK with Developers and Community.
c) We’ve already looking for a replacement for VSCode. The last year showed that VSCode is fully focused on JS/HTML/Icons/Hotkey coders and no one wants to discuss other perspectives of VSCode.
P.S: In any case, thanks for your efforts, especially for the 2016-2018 years!
P.S.S: Upcoming 1.42… 2 months since the last release! The MOST BLOCKER ISSUES were fixed:
I don’t have more comments.