Iteration Plan for October 2023

[kieferrm]

This plan captures our work in October. This is a 4-week iteration. We will ship in early November.

Endgame

• October 23, 2023: Endgame begins
• October 27, 2023: Endgame done

The endgame details for this iteration are tracked here.

Plan Items

Below is a summary of the top level plan items.

Legend of annotations:

Mark	Description
🏃	work in progress
✋	blocked task
💪	stretch goal for this iteration
🔴	missing issue reference
🔵	more investigation required to remove uncertainty
⚫	under discussion within the team
⬛	a large work item, larger than one iteration

Accessibility

• Accessibility issues, see query @meganrogge team

UX

• Update Figma toolkit to use color variables vscode-figma-toolkit#10 @daviddossett
• Update Figma templates to use Dark/Light Modern themes vscode-figma-toolkit#9 @daviddossett

Workbench

• 💪 Polish unfocused dimming feature vscode#191775 @Tyriar
• 💪 Support keyboard navigation between groups in quick picks vscode#149046 @TylerLeonhardt
• Maximize current file/tab/editor vscode#16927 @benibenj @bpasero
• Allow to hide editor title section entirely (tabs, breadcrumbs) vscode#33607 @benibenj
• 🏃 Improve Profiles Management UX vscode#192387 @sandy081 @hbons
• Support showing the activity bar in alternate layouts vscode#118692 @sandy081
• 🏃 Allow for floating windows vscode#10121 @bpasero @Tyriar
• Deprecate Windows 32-bit builds vscode-internalbacklog#4460 @joaomoreno

Code Editor

• Explore multiple diff editors in a single scrolling editor for PR diff reviewing vscode#179000 @hediet @lszomoru

Comments

• None.

Notebook Editor

• Improve notebook scrolling on execution vscode#194516 @amunger
• Improve stack trace handling and rendering vscode#195579 @amunger
• Support word highlight across notebook cell vscode#184259 @Yoyokrazy

Jupyter Notebooks

• Explore supporting Run Dependent Cells vscode-jupyter#14316 @rebornix
• Extension recommendation on datatype/mimetype vscode-jupyter#14315 @rebornix
• Explore moving Tensorboard support from Python extension to its own vscode-jupyter#14472 @DonJayamanne
• Explore requirements for Kernel API vscode-jupyter#14487 @DonJayamanne @rebornix
• 💪 Fix custom ZMQ build for Linux ARM32/ARM64 vscode-jupyter#14070 @DonJayamanne

WebAssembly Support

• 🏃 Investigate compile C# code in the browser to IL using dotnet.wasm vscode-wasm#112 @dbaeumer
• Explore resource model in WIT vscode-wasm#123 @dbaeumer

Languages

Python

• Contributions to the python extension, see plan @brettcannon team

Language Server Protocol

• Explore support WASM as a first class target for LSP servers in the LSP client vscode-languageserver-node#1337 @dbaeumer
• 🏃 LSP support to 3rd-parties vscode-python#21964 @karthiknadig

Source Control

• 🏃 Ahead/behind view in SCM view container vscode#192290 @lszomoru

Tasks

• None.

Testing

• Improve testing experience in self-hosting with extension test runner vscode#189680 @connor4312
• 💪 Design test coverage API vscode#123713 @connor4312

Debug

• 🏃 Explore rust-implemented memory profiler vscode-js-debug#1855 @connor4312

API

• API proposals: query @jrieken @mjbvz
• API finalization: query @jrieken @mjbvz

Extensions

• Explore support for extensions to provide additional data to the issue reporter vscode#46726 @justschen @TylerLeonhardt

Extension Contributions

• Improvements to the Remote extensions, see plan @roblourens @chrmarti @connor4312 @joyceerhl
• Support setting project when viewing a PR vscode-pull-request-github#4926 @alexr00

Documentation

• Scaffold "Custom Layout" document vscode-docs#6393 @gregvanl

Engineering

• Use Terrapin instead of crates.io for building the CLI vscode#195031 @connor4312
• Explore publishing the CLI to winget vscode#192885 @connor4312
• Track memory leaks in unit tests vscode#190503 team

Electron

• None.

---

Deferred

• Support PR comments in notebooks vscode-pull-request-github#3462 @alexr00
• Provide diff view inside comment card to preview suggested edits vscode#192129 @alexr00
• Support picking tab vs spaces in notebook cell editor vscode#108675 @Yoyokrazy
• Adopt canonical URI Provider API for workspace trust vscode#180582 @sbatten
• Automatic type acquisition on the web vscode#172887 @mjbvz
• 🏃 Explore support for multiple GitHub accounts vscode#127967 @TylerLeonhardt
• 🏃 Finalize port attributes API vscode#115616 @alexr00
• Review and update Command Line Interface (CLI) topic vscode-docs#6435 @gregvanl
• Review and update Configure C++ Debugging topic vscode-docs#5518 @gregvanl
• 🏃 Explore wiring Electron.net API into the utility process vscode#192899 @devm33 @deepak1556
• 🏃 Add smart pasting of markdown URLs vscode#186289 @mjbvz
• 🏃 Add drop/paste for css vscode#189875 @mjbvz
• 🏃 Add CA support to http2 requests in the extension host vscode#185098 @chrmarti
• Allow having shorter text when pinning in language status API vscode#192880 @jrieken

[RichCaloggero]

Instead of using visual descriptions of icons, then requiring a screen reader user to look up and remember the meaning of the icon (i.e. "personRunning" means "work in progress"), just use "work in progress" as the icon label.

[WatchTower001110]

from azure.ai.ml.entities import AmlCompute

Name assigned to the compute cluster

cpu_compute_target = "cpu-cluster"

try:
# let's see if the compute target already exists
cpu_cluster = ml_client.compute.get(cpu_compute_target)
print(
f"You already have a cluster named {cpu_compute_target}, we'll reuse it as is."
)

except Exception:
print("Creating a new cpu compute target...")

# Let's create the Azure Machine Learning compute object with the intended parameters
# if you run into an out of quota error, change the size to a comparable VM that is available.
# Learn more on https://azure.microsoft.com/en-us/pricing/details/machine-learning/.
cpu_cluster = AmlCompute(
    name=cpu_compute_target,
    # Azure Machine Learning Compute is the on-demand VM service
    type="amlcompute",
    # VM Family
    size="STANDARD_DS3_V2",
    # Minimum running nodes when there is no job running
    min_instances=0,
    # Nodes in cluster
    max_instances=4,
    # How many seconds will the node running after the job termination
    idle_time_before_scale_down=180,
    # Dedicated or LowPriority. The latter is cheaper but there is a chance of job termination
    tier="Dedicated",
)
print(
    f"AMLCompute with name {cpu_cluster.name} will be created, with compute size {cpu_cluster.size}"
)
# Now, we pass the object to MLClient's create_or_update method
cpu_cluster = Aml_client.compute.begin_create_or_update(cpu_cluster)

#195109 (comment)

[WatchTower001110]

az extension remove -n azure-cli-ml
az extension remove -n azure-cli-ml*