When `activateByEvent` is called with `ActivationKind.Immediate`, only
activate on local extension hosts (LocalProcess, LocalWebWorker) and
defer remote host activation until the remote host is ready. This
prevents blocking startup when extensions need immediate activation
but the remote host isn't available yet.
Changes:
- Add `activationKind` to `IWillActivateEvent` interface
- Track deferred activation events in `_pendingRemoteActivationEvents`
- Filter to local hosts only for Immediate activation
- Replay deferred events on remote hosts after initialization
- Fire `onWillActivateByEvent` again with Normal kind when replaying
Fixes#260061
* terminals in thinking dropdown
* make setting on by default:'
* fix chat confirmation widget
* fix spelling
* fix public issue
* add backup icon for terminal
* feat: enable win11 context menu for stable
* chore: update dll package
* chore: codesign appx for stable
* feat: support system setup
* fix: allow installing appx for system setup
* fix: add -SkipLicense to avoid exception during install
* Initial plan
* Fix 100% CPU on Windows when watched file is deleted
When a watched file/folder is deleted on Windows, Parcel's subscribe
callback may continue to receive errors from ReadDirectoryChangesW.
Previously, these errors were processed by onUnexpectedError which
would fire _onDidError events repeatedly. This caused 100% CPU usage
as the error handling loop never stopped.
The fix checks if the watcher has already failed (via watcher.failed)
before processing errors. When the watcher has failed (which happens
when the watched path is deleted), additional errors from Parcel are
ignored. This prevents the CPU spike while still allowing the normal
suspend/resume mechanism to handle watching the path when it's recreated.
Fixesmicrosoft/vscode#263718
Co-authored-by: bpasero <900690+bpasero@users.noreply.github.com>
* Update comments to better explain CPU issue prevention
Co-authored-by: bpasero <900690+bpasero@users.noreply.github.com>
* Add same fix to nodejs watcher for Windows CPU issue
Apply the same fix to nodejsWatcherLib.ts as suggested by the reviewer.
The error handler now checks if the watcher has already failed before
processing additional errors, preventing the endless error loop on
Windows when a watched path is deleted.
Co-authored-by: bpasero <900690+bpasero@users.noreply.github.com>
* lets not change parcel watcher for now
* .
* .
---------
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: bpasero <900690+bpasero@users.noreply.github.com>
Co-authored-by: Benjamin Pasero <benjamin.pasero@microsoft.com>
