* feat: expose gpu log messages as part of --status
This is useful in scenarios where the application rendering
completely breaks and we want to know the health of gpu process
on demand without having to restart the application.
The log messages are usually available on demand via
Developer: Show GPU Info page but during complete rendering failure
the developer page will also fail to render.
* feat: add support for argv.json switch to recover from failure
* chore: address feedback
* chore: update build
* chore: bump distro
* using relative values instead of absolute values for the font size and the line height
* renaming to multiplier
* setting back to font size and line height
* Revert "renaming to multiplier"
This reverts commit 5588855659.
* doing some polishing work
* changing the api
* updating to higher version of vscode-textmate
* also changing the vscode textmate package version for the remote extension
* increasing the vscode textmate version in remote/web
* updating package lock json
* using css variables instead of fetching font size from config service
* removing the second multiplier event
* adding ? after dom element style
* Ensure dots from floating fontSize are stripped from class names
---------
Co-authored-by: Alexandru Dima <alexdima@microsoft.com>
* Introduce compilation error
* Engineering - limit the tasks that we run
* Limit available memory to simulate an OOM
* Try to update the task
* Remove the use of npm-run-all
* Fix script
* Another try
* Try npm-run-all2
* Restore tasks, keep npm-run-all2
* Switch from npm-run-all to npm-run-all2
* Revert changes that were used for testing
Brings in further improvements to handling of write backpressure. After
this we no longer throttle at all which means that for older versions of
bash at least on macOS interleaving is possible, but pasting and sending
should be near instantaneous for any reasonable amount of text. I
measured zsh injesting 5mb of data in ~14 seconds.
See:
- microsoft/node-pty#835
- microsoft/node-pty#837
- microsoft/node-pty#839
Part of #246204, #283056
* Update conpty version in setting description
* Invalidate build cache
* Bump node-pty to 1.1.0-beta40
---------
Co-authored-by: Anthony Kim <anthonykim@microsoft.com>
* show inline install X recommendations for alternative agents
* polish
* move to ChatAgentRecommendation contribution
* fix incorrect registrations
* no f1
* update distro f7daaf6841
