- 13 5月, 2020 40 次提交
-
-
-
由 Johannes Rieken 提交于
-
由 Robo 提交于
-
由 Ladislau Szomoru 提交于
* Add a 1 second timeout for flushing the telemetry
-
由 Isidor Nikolic 提交于
Upload folders via D&D in the browser workbench
-
由 Martin Aeschlimann 提交于
-
由 Johannes Rieken 提交于
-
由 Johannes Rieken 提交于
-
由 Martin Aeschlimann 提交于
Support more shell script file extensions
-
由 Benjamin Pasero 提交于
-
由 Benjamin Pasero 提交于
-
由 Benjamin Pasero 提交于
-
由 Benjamin Pasero 提交于
-
由 João Moreno 提交于
-
由 Benjamin Pasero 提交于
-
由 Rachel Macfarlane 提交于
-
由 Rob Lourens 提交于
-
由 SteVen Batten 提交于
-
由 SteVen Batten 提交于
-
由 Sandeep Somavarapu 提交于
-
由 SteVen Batten 提交于
-
由 Rob Lourens 提交于
-
由 Rob Lourens 提交于
-
由 Aditya Thakral 提交于
-
由 Aditya Thakral 提交于
-
由 Sandeep Somavarapu 提交于
-
由 Connor Peet 提交于
* debug: filter exceptions from DAP telemetry on web This change will filter DAP keys beginning with `!` when the remote authority is "other", which SteVen recommended as a way to tell if we're on web/codespaces. Isidor mentioned previously that there was filtering for keys beginning with an underscore, but this was only applied to some data in error responses, not general telemetry events. An alternative approach to this is filtering exceptions based on the environment on the extension side, but I figured it would be better to have VS Code do that so that we don't end up with N many possibly deviant sets of environment detection logic. * fixup! pip exception filtering to a helper function
-
由 Connor Peet 提交于
-
由 Matt Bierner 提交于
This reverts commit cd93eaac. Fixes #97636
-
由 Matt Bierner 提交于
Fixes #95831
-
由 Matt Bierner 提交于
-
由 João Moreno 提交于
-
由 SteVen Batten 提交于
-
由 Martin Aeschlimann 提交于
-
由 Rob Lourens 提交于
-
由 João Moreno 提交于
-
由 Connor Peet 提交于
-
由 Miguel Solorio 提交于
-
由 SteVen Batten 提交于
-
由 Connor Peet 提交于
This change will filter DAP keys beginning with `!` when the remote authority is "other", which SteVen recommended as a way to tell if we're on web/codespaces. Isidor mentioned previously that there was filtering for keys beginning with an underscore, but this was only applied to some data in error responses, not general telemetry events. An alternative approach to this is filtering exceptions based on the environment on the extension side, but I figured it would be better to have VS Code do that so that we don't end up with N many possibly deviant sets of environment detection logic.
-