sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: New file using keyboard only in file explorer not working on macbook
Labels: bug,file-explorer

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 
Version: 1.96.4 (Universal)
Commit: cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba
Date: 2025-01-16T00:16:19.038Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.2.0
- OS Version: Sequoia 15.2

Steps to Reproduce:

1.  open any project in VSC
2. navigate to the file explorer using ⌘ ⇧ E (Command shift E)
3. navigate to the folder you want the file to be created in using arrow keys ⬆ ⬇ ⬅ to collapse folder, ➡ to expand folder
4. when the folder is selected press ⇧ F10 (default context menu for macbook) the menu appears

![Image](https://github.com/user-attachments/assets/365a9364-2f90-4a97-9ba2-29063b47e38c)

5. using arrows, select create folder, or create file and click enter
6. observe it will start renaming the folder in both cases, it doesn't matter if the folder is expanded or collapsed

![Image](https://github.com/user-attachments/assets/a8af0cad-dde1-48a6-8a05-6339fb11da6a)

Whereas if I'm using the physical mouse to to the same, it start the interaction correctly (unless you hadn't focussed the VSC, which causes the interaction to be buggy, but in this case it is not that)

![Image](https://github.com/user-attachments/assets/cc11e387-9422-4c6a-8bc2-288a0a7fe2d7)
Repository: rust
Issue: Missing Safety Guarantee in `merge_down` Function Documentation (`smallsort` Module)
Labels: A-docs,T-libs

### Location

The _SAFETY_ comment in question is located in the [`merge_down`](https://github.com/rust-lang/rust/blob/48ef38d3503a04e5e18157e664e3e65dc7eca1a5/library/core/src/slice/sort/shared/smallsort.rs#L721) function in the `smallsort` module in `shared` in `sort` in the `slice` module of the `core` crate.

### Summary

While working on the [Rust std-lib verification](https://github.com/model-checking/verify-rust-std), I identified a missing requirement in the _SAFETY_ comment in the [`merge_down`](https://github.com/rust-lang/rust/blob/48ef38d3503a04e5e18157e664e3e65dc7eca1a5/library/core/src/slice/sort/shared/smallsort.rs#L721) function in the `smallsort` module.

## Description of the problem

In the following code, the _SAFETY_ comment does not guarantee that `dst.sub(1)` remains within the same allocated object as `dst`. This violates one of the [safety requirements for `pointer.sub`](https://doc.rust-lang.org/std/primitive.pointer.html#safety-8).

```rust
unsafe fn merge_down<T, F: FnMut(&T, &T) -> bool>(
    mut left_src: *const T,
    mut right_src: *const T,
    mut dst: *mut T,
    is_less: &mut F,
) -> (*const T, *const T, *mut T) {
    // snip

    // SAFETY: The caller must guarantee that `left_src`, `right_src` are valid
    // to read and `dst` is valid to write, while not aliasing.
    unsafe {
        // snip
        dst = dst.sub(1);  // <- issue here
    }

    (left_src, right_src, dst)
}
```

## Proposed fix

Update the _SAFETY_ comment as follows.

```diff
    // SAFETY: The caller must guarantee that `left_src`, `right_src` are valid
-   // to read and `dst` is valid to write, while not aliasing.
+   // to read, `dst` is valid to write, while not aliasing, and `dst.sub(1)`
+   // is within the same allocated object as `dst`.
```

## `merge_up` does not have the same problem

Although the _SAFETY_ comment in the [`merge_up`](https://github.com/rust-lang/rust/blob/48ef38d3503a04e5e18157e664e3e65dc7eca1a5/library/core/src/slice/sort/shared/smallsort.rs#L688) function may appear to have a similar issue, I believe this is not the case. Since `dst` must already be valid for a write, `dst.add(1)` will remain within the bounds of the same allocated object.
Repository: vscode
Issue: Cannot open a terminal inside a dev container
Labels: info-needed,terminal


Type: <b>Bug</b>

It was working fine. Today when I re-opened, the terminals that weere already opened had like a disconnection symbol in red, but when hivering on it, there was no info.
I closed it completely and reopened, however, the issue persists: I cannot open any terminal. When I try to do so, some sort of ghost tab appears on the left Tags pannel (on the terminal section at the bottom), but no title, absolutely nothing happens.
I would really appreciate y anyone takes a look into it :)

VS Code version: Code 1.93.1 (Universal) (38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40, 2024-09-11T17:20:05.685Z)
OS version: Darwin arm64 24.1.0
Modes:
Remote OS version: Linux x64 6.10.14-linuxkit

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Apple M3 Pro (12 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|3, 3, 3|
|Memory (System)|18.00GB (0.26GB free)|
|Process Argv|--crash-reporter-id ec1e1863-9ec5-463a-a8b2-77556a5a69e4|
|Screen Reader|no|
|VM|0%|

|Item|Value|
|---|---|
|Remote|Dev Container: Existing Docker Compose (Extend) @ desktop-linux|
|OS|Linux x64 6.10.14-linuxkit|
|CPUs|unknown (12 x 0)|
|Memory (System)|7.65GB (1.26GB free)|
|VM|0%|
</details><details><summary>Extensions (16)</summary>

Extension|Author (truncated)|Version
---|---|---
vsc-python-indent|Kev|1.19.0
jupyter-keymap|ms-|1.1.2
remote-containers|ms-|0.394.0
remote-ssh|ms-|0.115.1
remote-ssh-edit|ms-|0.87.0
remote-wsl|ms-|0.88.5
vscode-remote-extensionpack|ms-|0.26.0
remote-explorer|ms-|0.4.3
remote-server|ms-|1.5.2
pdf|tom|1.2.2
copilot|Git|1.250.0
copilot-chat|Git|0.20.3
vscode-docker|ms-|1.29.4
debugpy|ms-|2024.14.0
python|ms-|2024.14.1
vscode-pylance|ms-|2024.12.1


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupytercf:31046870
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc1:31192215
cf971741:31144450
iacca1:31171482
notype1cf:31157160
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624
dwoutputs:31217127
hdaa2157:31222309
copilot_t_ci:31222730

```

</details>

<!-- generated by issue reporter -->
Repository: ollama
Issue: burn windows update at the stake
Labels: feature request

Listen, Its 5am, I am tired, I dont want to be awake anymore, if this makes any sense or is logically possible, please do ANYTHING

I just posted [this](https://www.reddit.com/r/ollama/comments/1i8spym/recovering_lost_model_files_due_to_forced_windows/) to the subreddit

Hours and hours lost to windows update. **Please just automatically turn it off while downloading models.**

when downloading `net stop wuauserv` or whatever you need to do.

While writing the reddit post, I was again prompted to update windows. Mid recovery attempt. 

WHEN WRITING THIS, I HAVE AGAIN BEEN PROMPTED TO UPDATE WINDOWS, AFTER I TOLD IT "I DONT WANT TO UPDATE"

![Image](https://github.com/user-attachments/assets/732c52b6-422c-4bc4-96c1-effcd4f2d420)
(my server is on the wrong timezone for some reason. i dont care to fix it)

You have no idea the pain and rage that consumes me.

Please save others from knowing what I know........
Repository: kubernetes
Issue: [Flaking test] [sig-node] Kubernetes e2e suite.[It] [sig-node] Pods Extended Pod Container Status should never report container start when an init container fails
Labels: sig/node,kind/flake,needs-triage

### Which jobs are flaking?

master-blocking
- gce-ubuntu-master-containerd

### Which tests are flaking?

Kubernetes e2e suite.[It] [sig-node] Pods Extended Pod Container Status should never report container start when an init container fails
[Prow](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-ubuntu-gce-containerd/1882490406982127616)
[Triage](https://storage.googleapis.com/k8s-triage/index.html?test=ods%20Extended%20Pod%20Container%20Status%20should%20never%20report%20container%20start%20when%20an%20init%20container%20fails&xjob=e2e-kops)

### Since when has it been flaking?

[1/15/2025, 1:23:19 PM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-ubuntu-ec2-arm64-containerd/1879564729022681088)
[1/20/2025, 7:25:30 PM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-ubuntu-ec2-containerd/1881467771536019456)
[1/21/2025, 7:26:40 PM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-ubuntu-ec2-arm64-containerd/1881830414499188736)
[1/22/2025, 1:24:08 AM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-ec2-eks-al2023-arm64/1881920257635913728)
[1/23/2025, 3:07:44 PM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-ubuntu-gce-containerd/1882490406982127616)

### Testgrid link

https://testgrid.k8s.io/sig-release-master-blocking#gce-ubuntu-master-containerd

### Reason for failure (if possible)

```
{ failed [FAILED] 1 errors:
pod pod-terminate-status-2-10 on node bootstrap-e2e-minion-group-5d4d container unexpected exit code 2: start=2025-01-23 18:26:43 +0000 UTC end=2025-01-23 18:26:44 +0000 UTC reason=Error message=
In [It] at: k8s.io/kubernetes/test/e2e/node/pods.go:548 @ 01/23/25 18:27:35.688
}
```

### Anything else we need to know?

N/A

### Relevant SIG(s)

/sig node
cc: @kubernetes/release-team-release-signal
Repository: ollama
Issue: Error: server metal not listed in available servers map
Labels: bug

### What is the issue?

I downloaded Ollama today on my Macbook (Apple M3 Pro, with MacOS Sonoma 14.3 23D56), and tried to run deepseek-r1:8b, but ollama failed with this error:

> $ ollama run deepseek-r1:8b
> Error: [0] server metal not listed in available servers map[]

p.s. I can run this model with llama-cli on the same device.

### OS

macOS

### GPU

Apple

### CPU

Apple

### Ollama version

0.5.7
Repository: ollama
Issue: Error when trying to download  deepseek-r1:7b
Labels: bug

### What is the issue?

I tried using ollama run deepseek-r1:7b
It started to download for a minute then this error appeared
Error: Post "http://127.0.0.1:11434/api/show": dial tcp 127.0.0.1:11434: connectex: No connection could be made because the target machine actively refused it.

### OS

Windows

### GPU

Nvidia

### CPU

AMD

### Ollama version

0.5.7
Repository: flutter
Issue: Add ability to tree shake icon for rfw
Labels: package,team-ecosystem,p: rfw

### Use case

Example code:
```
import 'package:flutter/widgets.dart';
import 'package:rfw/rfw.dart';

void main() {
  final runtime = Runtime()
    ..update(const LibraryName(['core']), createCoreWidgets());

  runApp(
    RemoteWidget(
      runtime: runtime,
      data: DynamicContent(),
      widget: const FullyQualifiedWidgetName(LibraryName(['remote']), 'root'),
    ),
  );
}
```
Try to build in profile mode:
`flutter build apk --profile`

Build failed and below is the log.

```
This application cannot tree shake icons fonts. It has non-constant instances of IconData at the following locations:
  - file:///Users/zhenhao.ng/.pub-cache/hosted/pub.dev/rfw-1.0.30/lib/src/flutter/argument_decoders.dart:806:12
Target aot_android_asset_bundle failed: Error: Avoid non-constant invocations of IconData or try to build again with --no-tree-shake-icons.
```

### Proposal

Let us do tree shaking on the IconData
Repository: transformers
Issue: ZeroShotClassificationArgumentHandler should be explicit it has a somewhat unsafe internal behaviour.
Labels: Feature request

### Feature request

Currently, `ZeroShotClassificationArgumentHandler::__call__` will execute https://github.com/huggingface/transformers/blob/main/src/transformers/pipelines/zero_shot_classification.py#L41 , that is, it will call python `.format()` on the hypothesis provided to format the label in it, while allowing the full extent of .format() placeholders syntax, which is quite large.

For example, passing `hypothesis_template = "{:>9999999999}"` and any label will happily eat 100Go of RAM because the whole scope of python formatting is allowed.

This is not made clear annywhere, but library users need to know they have to sanitize those inputs very carefully.

I think that at least the docstring of the class, and ideally the reference doc for "hypothesis_template" on https://huggingface.co/docs/huggingface_hub/package_reference/inference_client#huggingface_hub.InferenceClient.zero_shot_classification should be updated to mention this, it's quite important for users of the lib (in particular for parameters that will naturally tend to be user facing in the end).

Alternatively, this call could accept {} only as a placeholder, it's hard to see a legitimate use case for exotic formatting of labels in the hypothesis template.

Thanks :-) 

### Motivation

I think it's good to help the internet be a safer place in general :-) 

### Your contribution

It's unclear to me whether I can contribute to the documentation on hugginface.com.

I could contribute a fix to be stricter on allowed hypothesis_template in transformers though if you want to take this route (I'm pretty sure even an AI model could contribute the two lines needed though...)
Repository: vscode
Issue: Allow customization of editor tab height and editor tab bar scrollbar height
Labels: feature-request,workbench-tabs

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
I would like to be able to customize the height of tabs and of the scrollbar in the tab bar. There are options to adjust the size of these but they're really only choices between small and smaller.

I always find myself fighting with the minuscule scrollbar and inadvertently clicking other open files. It gets frustrating when it happens dozens of times in the same session.

If these were customizable in a way similar to how you can set rulers in the editor, it would not remove current functionality for users who want these to be tiny, and it would make it easier for users needing them to be larger(for disabilities or other reasons).

Thank you!
Repository: deno
Issue: Repl prints an error twice
Labels: repl

Version: Deno 2.1.7

1. Run `deno` to start the repl
2. Execute `for (console.log("a") of [1]);`

It reports the syntax error twice:
```
➜ deno            
Deno 2.1.7
exit using ctrl+d, ctrl+c, or close()
REPL is running with all permissions allowed.
To specify permissions, run `deno repl` with allow flags.
> for (console.log("a") of [1]);
error: The left-hand side of an assignment expression must be a variable or a property access. at file:///repl.tsx:1:6

  for (console.log("a") of [1]);
       ~~~~~~~~~~~~~~~~

The left-hand side of an assignment expression must be a variable or a property access. at file:///repl.tsx:1:6

  for (console.log("a") of [1]);
       ~~~~~~~~~~~~~~~~
```

This is not a SWC bug (in their playground they only report it once), and I couldn't find other syntax errors that are printed twice.

I cannot find any other error for which this happens.
Repository: pytorch
Issue: `torch.ops.aten.copy` causes SIGSEGV when handling sparse CSR tensors with invalid metadata
Labels: module: sparse,module: crash,triaged

### 🐛 Describe the bug

Using torch.ops.aten.copy with sparse CSR tensors can cause a segmentation fault (SIGSEGV). The issue appears to stem from a lack of validation for the sparse tensor metadata (crow_indices, col_indices, and values). When the metadata contains invalid or uninitialized data (e.g., due to torch.randn generating sparse CSR tensors with incomplete initialization), torch.ops.aten.copy attempts to access this data directly, leading to undefined behavior and a crash.

example:

```python
import torch

print(torch.__version__)

# Create sparse CSR tensors with torch.randn
sym_0 = (5, 5)
sym_1 = torch.sparse_csr

var_1 = torch.randn(size=sym_0, layout=sym_1)  # Generates sparse CSR tensor
var_2 = torch.randn(size=sym_0, layout=sym_1)

# Attempt to copy data
res = torch.ops.aten.copy(var_1, var_2)
print(res)
```

Observed behavior:

```
2.7.0.dev20250116+cu124
/home/user/test.py:8: UserWarning: Sparse CSR tensor support is in beta state. 
If you miss a functionality in the sparse tensor support, please submit a feature request to https://github.com/pytorch/pytorch/issues. 
(Triggered internally at /pytorch/aten/src/ATen/SparseCsrTensorImpl.cpp:53.)
var_1 = torch.randn(size=sym_0, layout=sym_1)
fish: Job 2, 'python3 test.py' terminated by signal SIGSEGV (Address boundary error)
```

### Versions

PyTorch version: 2.7.0.dev20250116+cu124
Is debug build: False
CUDA used to build PyTorch: 12.4
ROCM used to build PyTorch: N/A

OS: Manjaro Linux (x86_64)
GCC version: (GCC) 14.2.1 20240805
Clang version: 18.1.8
CMake version: version 3.30.2
Libc version: glibc-2.40

cc @alexsamardzic @nikitaved @pearu @cpuhrsch @amjames @bhosmer @jcaip
Repository: TypeScript
Issue: Type variables in type abstractions are not properly concretized
Labels: Bug,Fix Available

### 🔎 Search Terms

type variables unknown

### 🕗 Version & Regression Information

- This changed between versions 4.9.5 and 5.0.4.

### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=5.7.3#code/MYewdgzgLgBAZjAvDAPADQDQD4AUBzALlQEFscAjItASiSxkxgitsXrxwmoG4AoX0JFgAnAKaxkcHCgBCZAB5EZregEYMMAETRhmnrwD0BmCZgA9APxA

### 💻 Code

```ts
const f = <X,>(g: <A,>(b: X) => X, s: X) => g(s);

const ret = f(<B,>(x: B) => 1, "str");
//    ^? const ret: unknown
```


### 🙁 Actual behavior

No type error is reported and `ret` is inferred as `unknown` type.

### 🙂 Expected behavior

I think a type error is reported because the call to `f` attempts to concretize the type variable X  not only as a number but also as a string. In fact, TypeScript 4.9.5 reported a type error.


### Additional information about the issue

I am not sure that TypeScript 4.9.5 was perfect. The following code is inferred to be `unknown`, but I think `string` is correct. This behavior was back to TypeScript 3.5.1.

```ts
const f = <X,>(g: <A,>(b: X) => X, s: X) => g(s);

const ret = f(<B,>(x: B) => x, "str");
//    ^? const ret: unknown

// actual: ret is inferred as unknown
// expected: ret is inferred as string
```
https://www.typescriptlang.org/play/?ts=5.7.3#code/MYewdgzgLgBAZjAvDAPADQDQD4AUBzALlQEFscAjItASiSxkxgitsXrxwmoG4AoX0JFgAnAKaxkcHCgBCZAB5EZrevIwwARNGEaevAPT6YxmAD0A-P0MwAhsCgBXGwBsiY2AEsIMD2DijhMQATW28HMABrMBAAdzADI1F5AAdRe1Egt3Efb19-QIzQpihhXzwgA

I also found a strange behavior that a type variable that should have been concretized was returned without being concretized. I thought this is related, but I could be wrong. Sorry if so.

```ts
const f = <X,>(g: <A,>(x: X) => X) => g<string>;

const h = f<number>(<B,>(x: number) => 1);
//    ^? const h: (x: X) => X

h(1);
// actual: type error
// expected: no type error
```
https://www.typescriptlang.org/play/?ts=5.7.3#code/MYewdgzgLgBAZjAvDAPADQDQD4AUBzALlQEFscAPItASiSxhrpjxWgCcBLMPLAbgCh+oSLAAWSeCjABXALYAjAKZtcKAEJlKMGQuW1E9AIzUBAelMxLMAHoB+QaJzGzFgIbAo01wBsiUAJ4ADoowymwgbPzmoeTBHooAJkRgIDABwaFs4WxAA
Repository: ollama
Issue: Model loaded each time
Labels: bug

### What is the issue?

Model reload each time it's need the internet to load  when i terminate the cmd and run again 

![Image](https://github.com/user-attachments/assets/cfe596be-53e6-458b-a84e-a60194e39d9c)

### OS

_No response_

### GPU

_No response_

### CPU

Intel

### Ollama version

0.5.4
Repository: next.js
Issue: Automatically adding initial-scale to meta viewport
Labels: Metadata

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/fervent-microservice-fxis37?fork=true

### To Reproduce

1. open root layout.tsx
2. add 
```
export const viewport: Viewport = {
  width: 390,
  userScalable: false,
};
```

### Current vs. Expected behavior

**Current**
`<meta name="viewport" content="width=390, initial-scale=1, user-scalable=no">`

**Expected**
`<meta name="viewport" content="width=390, user-scalable=no">`

initial-scale is not expected here as default and I am not be able to remove it. I expect full control over meta viewport tag.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.2.0: Fri Dec  6 18:56:34 PST 2024; root:xnu-11215.61.5~2/RELEASE_ARM64_T6020
  Available memory (MB): 16384
  Available CPU cores: 12
Binaries:
  Node: 22.10.0
  npm: 10.9.0
  Yarn: N/A
  pnpm: 8.15.1
Relevant Packages:
  next: 15.1.6 // Latest available version is detected (15.1.6).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: N/A
Next.js Config:
  output: N/A
```

### Which area(s) are affected? (Select all that apply)

Metadata

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local), Vercel (Deployed), Other (Deployed)

### Additional context

_No response_
Repository: vscode
Issue: Source Control is missing a disable for this file option
Labels: info-needed


Type: <b>Feature Request</b>

After I enabled source control for my project file, it was annoying to see the green text so I wanted to turn it off but there is no option for that, please look forward to it.

VS Code version: Code 1.96.4 (cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba, 2025-01-16T00:16:19.038Z)
OS version: Windows_NT x64 10.0.26100
Modes:


<!-- generated by issue reporter -->