sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Some `-Ctarget-feature`s must be restrained on RISCV
Labels: T-compiler,C-bug,O-riscv,A-floating-point,A-ABI,E-needs-investigation

refs:
- https://github.com/rust-lang/rust/issues/114544
  - https://github.com/rust-lang/rust/pull/116485 which was massively scaled back due to this open question
- https://github.com/rust-lang/rust/issues/116344
- https://github.com/rust-lang/rust/pull/129884
- https://github.com/rust-lang/rust/issues/131799
- https://github.com/rust-lang/rust/pull/131807

in discussion of the target modifiers RFC[^1], Ralf asks this question:

> That's actually fine on most targets, e.g. on x86 if you set the soft-float target feature then you can enable x87 and SSE and whatnot and keep using the soft-float ABI. Only aarch64 https://github.com/llvm/llvm-project/issues/110632 (from the targets I checked so far).
>
> The interesting question is what happens on RISC-V when I disable the FP instructions on a target that usually uses the hardfloat ABI. Sadly, what LLVM usually does in that case is silently fall back to the softfloat ABI. But I haven't checked for RISC-V.

cc @beetrees 

[^1]: https://github.com/rust-lang/rfcs/pull/3716
Repository: terminal
Issue: [High Contrast] "Failed to reload settings" warning isn't legible
Labels: Help Wanted,Issue-Bug,Area-Accessibility,Product-Terminal,Priority-3

![Image](https://github.com/user-attachments/assets/93024e28-1b51-4837-b1d2-aff44a212536)
Repository: vscode
Issue: Allow settings with object widgets to configure labels for `item`/`value`
Labels: feature-request,settings-editor

For object settings such as `files.associations`, it would nice if settings could customize the labels for `item`/`value` used in the settings ui


![Image](https://github.com/user-attachments/assets/ef1de45e-148a-4c99-b6e6-752775ccb50c)


This may help user understand how to configure these

Related it may also be nice to have hover tooltips on the `item`/`value` headings
Repository: pytorch
Issue: Better mergebot messages when reverting a PR
Labels: module: ci,triaged

### 🐛 Describe the bug

See https://github.com/pytorch/pytorch/pull/139399#issuecomment-2455961719 - just message appearing out of nowhere giving now explanation why anyone want to revert the PR... (I suspect the reason is because mergebot incorrectly believes this PR and https://github.com/pytorch/pytorch/pull/139358 are dependent, but they are not)

### Versions

CI

cc @seemethere @pytorch/pytorch-dev-infra
Repository: vscode
Issue: Validate tool input
Labels: feature-request,api

We should validate the input/parameters of LanguageModelTool calls. We could extract part of the json language-service into vscode to do this.
Repository: tensorflow
Issue: WSL instruction outdated
Labels: stat:awaiting tensorflower,wsl2

Page URL: https://www.tensorflow.org/install/pip#windows-wsl2

At this point in time Ubuntu 24.04 requires (or, recommends) using a virtual environment to install Python packages. As a result, the following command will no longer work in WSL:

```
python3 -m pip install tensorflow[and-cuda]
```

Below is a summary of commands needed to set up a virtual environment and install Tensorflow with the CUDA libraries.

```
sudo apt install python3-venv

python3 -m venv tf

source ~/tf/bin/activate

pip install tensorflow[and-cuda]
```
Repository: rust
Issue: rustdoc search: trait methods should not show the same as inherent methods
Labels: T-rustdoc,C-discussion,A-rustdoc-search

did a search for "unchecked" and found this confusing snippet:

![tuple::get_unchecked_mut](https://github.com/user-attachments/assets/a98a06c1-fa1f-4c47-83a9-4f6d12ca9324)

this the SliceIndex trait method.

additionally, perhaps implementations of trait methods should be deprioritized during name-based search?
Repository: ui
Issue: [bug]: Text size on mobile accordion
Labels: bug

### Describe the bug

The size of the text shrinks when you open an accordion on mobile. It seems to happen when you open one accordion then open the very next one after it

### Affected component/components

Accordion

### How to reproduce

1. Open an accordion on mobile
2. Open the very next accordion after it and the text will be smaller

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Android, Chrome
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: vscode
Issue: Implicit context widget isn't deduplicated against other attachments
Labels: bug,panel-chat

1. Have a file open in the editor and chat view open
2. From the editor context menu, the context picker, or DnD, attach the active editor to chat
3. :bug: the implicit context widget is still there, I would expect it to go away in favor of the persistent attachment and then come back the next time I open a file that isn't already attached
Repository: vscode
Issue: Consider changing command name `Start in Editor with Current line`
Labels: under-discussion,inline-chat

I'm aligning the terminal context menu items/command in https://github.com/microsoft/vscode-copilot/issues/10149 and after that we have:

![Image](https://github.com/user-attachments/assets/ed84ce92-6d89-40e2-a804-3144d7b2f596)

Should `Start in Editor with Current line` become `Editor Inline Chat with Current Line`?
Repository: langchain
Issue: create_retrieval_chain verbose not working
Labels: 🤖:bug

### Checked other resources

- [X] I added a very descriptive title to this issue.
- [X] I searched the LangChain documentation with the integrated search.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I am sure that this is a bug in LangChain rather than my code.
- [X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

### Example Code

```
from langchain.chains import create_retrieval_chain
retrieval_chain = create_retrieval_chain(retriever, combine_docs_chain, verbose=True)
rag_chain.invoke({"input": question})
```

No verbose outcome.

### Error Message and Stack Trace (if applicable)

_No response_

### Description

qa_chain = load_qa_chain(chat, verbose=True) is possible

retrieval_chain = create_retrieval_chain(retriever, combine_docs_chain) is not allowed to have a verbose.

### System Info


System Information
------------------
> OS:  Linux
> OS Version:  #1 SMP PREEMPT_DYNAMIC Thu Jun 27 21:05:47 UTC 2024
> Python Version:  3.10.12 (main, Sep 11 2024, 15:47:36) [GCC 11.4.0]

Package Information
-------------------
> langchain_core: 0.3.15
> langchain: 0.3.7
> langchain_community: 0.3.5
> langsmith: 0.1.137
> langchain_text_splitters: 0.3.0

Optional packages not installed
-------------------------------
> langgraph
> langserve

Other Dependencies
------------------
> aiohttp: 3.10.10
> async-timeout: 4.0.3
> dataclasses-json: 0.6.7
> httpx: 0.27.2
> httpx-sse: 0.4.0
> jsonpatch: 1.33
> numpy: 1.26.4
> orjson: 3.10.10
> packaging: 24.1
> pydantic: 2.9.2
> pydantic-settings: 2.6.1
> PyYAML: 6.0.2
> requests: 2.32.3
> requests-toolbelt: 1.0.0
> SQLAlchemy: 2.0.35
> tenacity: 9.0.0
> typing-extensions: 4.12.2
Repository: node
Issue: More benchmarks for the `node:test` module.
Labels: benchmark,test_runner

The `benchmark/test_runner` folder currently contains benchmarks for `it` and `describe` functions. I suggest we expand these benchmarks to cover additional test runner features, including mocks, coverage, and various test modes.

Here are the functions that (IMO) should be benchmarked:

## Basic Testing

These tests should run with a custom reporter without any special logic to make the tests as accurate as possible.

- [ ] `test`
	- [ ] Create a `test`
	- [ ] Create a `test` when it's not running due to `only`
	- [ ] Add a subtest
	- [ ] Skip a test
		- [ ] Via `skip: true`
		- [ ] Via `t.skip()`
		- [ ] Via `t.skip(...)`
	- [ ] TODO tests
		- [ ] Via `todo: true`
		- [ ] Via `t.todo()`
		- [ ] Via `t.todo(...)`

## Hooks
- [ ] `beforeEach`
- [ ] `afterEach`
- [ ] `before`
- [ ] `after`

## Reporters (#55757)
- [x] `dot`
- [x] `junit`
- [x] `spec`
- [x] `tap`
- [x] `lcov`

## Mocking
- [x] `mock.fn` (#55771)
- [ ] `mock.timers` for each API, and each sub-function
- [ ] `mock.module`

## Snapshots 
- [ ] `snapshot.setDefaultSnapshotSerializers(serializers)`
- [ ] `snapshot.setResolveSnapshotPath(fn)`
- [ ] `t.assert.snapshot`

## `Coverage`
Use `--expose-internals` to exclusively test the coverage part
- [ ] Basic
- [ ] Excluding files
- [ ] Including files
- [ ] With source maps
Repository: ui
Issue: [bug]: Sidebar toggle not working properly on mobile view.
Labels: bug

### Describe the bug

for my mobile and from the inspect element mobile view. The sidebar toggle not working at all for me.

### Affected component/components

Sidebar.tsx

### How to reproduce

![image](https://github.com/user-attachments/assets/f6584db1-db3a-4d56-bda8-7649863dc29d)


### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Chrome, Ubuntu.
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: pytorch
Issue: `softmax` fails to commute with `permute` / `transpose`
Labels: module: nn,triaged

### 🐛 Describe the bug

It should be the case that `sometensor.softmax(dim=d)` is the same as `sometensor.permute(...).softmax(dim=0).permute(...)` if the permutations are inverses.  This is not the case, at least for float32:
```python
import torch

val = torch.tensor([[7.76308536529541015625, 7.17303562164306640625, 5.13778305053710937500]], dtype=torch.float32, device='cpu')
val1 = val.softmax(dim=1, dtype=torch.float32).permute(1, 0)
val2 = val.permute(1, 0).softmax(dim=0, dtype=torch.float32)
print(val1)
print(val2)
print((val1 - val2).abs().max())
```
```
tensor([[0.6147],
        [0.3407],
        [0.0445]])
tensor([[0.6147],
        [0.3407],
        [0.0445]])
tensor(2.9802e-08)
```
Note that, e.g., scipy, does not have this issue:
```python
import numpy as np
from scipy.special import softmax

val = np.array([[7.76308536529541015625, 7.17303562164306640625, 5.13778305053710937500]], dtype=np.float32)
val -= val.max()
val1s = softmax(val, axis=1).T
val2s = softmax(val.T, axis=0)
print(val1s)
print(val2s)
print(np.max(np.abs(val1s - val2s)))
print()
print(val1 - val1s)
print(val2 - val2s)
```
gives
```
[[0.6147349 ]
 [0.34074736]
 [0.04451779]]
[[0.6147349 ]
 [0.34074736]
 [0.04451779]]
0.0

tensor([[0.0000e+00],
        [2.9802e-08],
        [0.0000e+00]])
tensor([[0.],
        [0.],
        [0.]])
```

Discrepancy originally encountered by @ronakrm (I have not looked for what floating point values give different results under transpose)

### Versions

Collecting environment information...
PyTorch version: 2.4.1
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 15.0.1 (arm64)
GCC version: Could not collect
Clang version: 16.0.0 (clang-1600.0.26.3)
CMake version: Could not collect
Libc version: N/A

Python version: 3.11.9 (main, Jul 30 2024, 20:31:18) [Clang 15.0.0 (clang-1500.3.9.4)] (64-bit runtime)
Python platform: macOS-15.0.1-arm64-arm-64bit
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Apple M3 Pro

Versions of relevant libraries:
[pip3] eintorch==0.2.5
[pip3] mypy==1.11.2
[pip3] mypy-extensions==1.0.0
[pip3] numpy==2.1.1
[pip3] pytorch-lightning==2.4.0
[pip3] torch==2.4.1
[pip3] torchmetrics==1.4.2
[pip3] torchvision==0.19.1
[conda] numpy                     2.0.0           py310h52bbd9b_0    conda-forge

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: PowerToys
Issue: Add PowerToys shortcuts to "Shortcut Guide"
Labels: Needs-Triage

### Description of the new feature / enhancement

It would be helpful to have a quick way to see all active PowerToys shortcuts within the "Shortcut Guide," rather than manually opening the tool and searching for each one. 

Having these shortcuts readily available in the guide, possibly in a different color to distinguish them from standard Windows shortcuts, would improve accessibility and usability.

### Scenario when this would be used?

When working on tasks that require multiple PowerToys tools—like resizing images, managing windows, or using FancyZones for layout management—users might need to quickly reference which shortcuts are available without disrupting their workflow. Instead of opening PowerToys settings, the "Shortcut Guide" could provide an at-a-glance view of relevant PowerToys shortcuts, enabling smoother multitasking and reducing interruptions.

### Supporting information

_No response_
Repository: react
Issue: [Compiler Bug]: Does not check for ref access in setState initial value function
Labels: Type: Bug,Component: Optimizing Compiler

### What kind of issue is this?

- [X] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAMygOzgFwJYSYAEAKgmDgBQCURwAOsUXIRUTgIYBGASgmkQC8RKGAR80NRkRFiAypxwJKNIQD523CQDo4sGAkw5qAbkYBfEOaA

### Repro steps

The playground compiles, but it should fail (Rules of React)

### How often does this bug happen?

Every time

### What version of React are you using?

latest playground

### What version of React Compiler are you using?

latest playground
Repository: puppeteer
Issue: [Bug]: No location or stack trace for Firefox console messages
Labels: bug,confirmed,bidi,P3,firefox

### Minimal, reproducible example

```TypeScript
const puppeteer = require("puppeteer");
const http = require("http");

let server = http.createServer((req, res) => res.end());
server.listen(8080, async () => {
	await test("chrome");
	await test("firefox");
	process.exit(0);
});

async function test(engine) {
	console.log(`Testing ${engine}`);
	let browser = await puppeteer.launch({
		browser: engine
	});
	
	let page = await browser.newPage();
	page.on("console", log => {
		console.log("Location:", log.location());
		console.log("Stack trace:", log.stackTrace());
	});
	await page.goto("http://localhost:8080", {
		waitUntil: "networkidle0"
	});
	await page.evaluate(() => {
		console.log("This is a log");
	});
}
```


### Background

When running on Firefox, `ConsoleMessage`s have no `location()` or `stackTrace()` information.

### Expectation

Expected output:
```
Testing chrome
Location: {
  url: 'pptr:evaluate;test%20(%2Fworkspaces%2Ftest%2Fbug.js%3A25%3A13)',
  lineNumber: 1,
  columnNumber: 10
}
Stack trace: [
  {
    url: 'pptr:evaluate;test%20(%2Fworkspaces%2Ftest%2Fbug.js%3A25%3A13)',
    lineNumber: 1,
    columnNumber: 10
  }
]
Testing firefox
Location: {
  url: 'pptr:evaluate;test%20(%2Fworkspaces%2Ftest%2Fbug.js%3A25%3A13)',
  lineNumber: 1,
  columnNumber: 10
}
Stack trace: [
  {
    url: 'pptr:evaluate;test%20(%2Fworkspaces%2Ftest%2Fbug.js%3A25%3A13)',
    lineNumber: 1,
    columnNumber: 10
  }
]
```

### Reality

Actual output:
```
Testing chrome
Location: {
  url: 'pptr:evaluate;test%20(%2Fworkspaces%2Fholoprint%2Fbug.js%3A25%3A13)',
  lineNumber: 1,
  columnNumber: 10
}
Stack trace: [
  {
    url: 'pptr:evaluate;test%20(%2Fworkspaces%2Fholoprint%2Fbug.js%3A25%3A13)',
    lineNumber: 1,
    columnNumber: 10
  }
]
Testing firefox
Location: {}
Stack trace: []
```

### Puppeteer configuration file (if used)

_No response_

### Puppeteer version

23.7.0

### Node version

20.17.0

### Package manager

npm

### Package manager version

10.8.2

### Operating system

Linux
Repository: yt-dlp
Issue: Localizing log messages
Labels: enhancement,triage

### DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

- [X] I understand that I will be **blocked** if I *intentionally* remove or skip any mandatory\* field

### Checklist

- [X] I'm requesting a feature unrelated to a specific site
- [X] I've looked through the [README](https://github.com/yt-dlp/yt-dlp#readme)
- [X] I've verified that I have **updated yt-dlp to nightly or master** ([update instructions](https://github.com/yt-dlp/yt-dlp#update-channels))
- [X] I've searched [known issues](https://github.com/yt-dlp/yt-dlp/issues/3766) and the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues **including closed ones**. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)

### Provide a description that is worded well enough to be understood

Implement localization of command line log messages for non-English speakers
Japanese, Chinese , etc
(I used Google Translate to write)

### Provide verbose output that clearly demonstrates the problem

- [ ] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [ ] If using API, add `'verbose': True` to `YoutubeDL` params instead
- [ ] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below

### Complete Verbose Output

_No response_
Repository: PowerToys
Issue: 寻找鼠标
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.80.1

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Mouse Utilities

### Steps to reproduce

寻找鼠标的时候只考虑了移动速度， 希望可以在原地晃动的时候不触发

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: vscode
Issue: Search Only in Open Editors does not work if file name has square bracket
Labels: bug,search

<!-- ⚠️⚠️ 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: 1.94.2
- OS Version: Windows 11

Steps to Reproduce:

1. Name a file with closed or open square brackets []
2. Open in editor and search only in open editors
![Image](https://github.com/user-attachments/assets/d5ce22f3-95c8-425f-bc51-9d0ebb89818e)
Repository: material-ui
Issue: [Autocomplete] ListboxProps external ref warning in vs code
Labels: typescript,component: autocomplete,v5.x,v6.x

### Steps to reproduce

Link to live example: https://codesandbox.io/p/sandbox/listboxprops-ref-bn67hk?file=%2Fsrc%2FAutocomplete.tsx

### Current behavior

_No response_

### Expected behavior

_No response_

### Context

Unable to build project due to typescript issue/warning

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: Windows 11 10.0.22631
  Binaries:
    Node: 19.1.0 - C:\Program Files\nodejs\node.EXE
    npm: 8.19.3 - C:\Program Files\nodejs\npm.CMD
    pnpm: Not Found
  Browsers:
    Chrome: Not Found
    Edge: Chromium (129.0.2792.89)
  npmPackages:
    @emotion/react: 11.10.5 => 11.10.5
    @emotion/styled: 11.10.5 => 11.10.5
    @mui/base:  5.0.0-alpha.103
    @mui/core-downloads-tracker:  5.15.20
    @mui/icons-material: ^5.11.9 => 5.15.20
    @mui/lab: 5.0.0-alpha.105 => 5.0.0-alpha.105
    @mui/material: 5.10.11 => 5.10.11
    @mui/private-theming:  5.15.20
    @mui/styled-engine:  5.15.14
    @mui/system:  5.15.20
    @mui/types:  7.2.14
    @mui/utils:  5.15.20
    @mui/x-data-grid: 5.17.9 => 5.17.9
    @types/react: 18.0.24 => 18.0.24
    react: 18.2.0 => 18.2.0
    react-dom: 18.2.0 => 18.2.0
    typescript: 4.8.4 => 4.8.4
```
</details>


**Search keywords**: [Autocomplete] ListboxProps external ref warning in vs code
Repository: vscode
Issue: Settings item loses focus unexpectedly
Labels: bug,settings-editor,confirmation-pending


Type: <b>Bug</b>

1. Open settings panel
2. Change some items, like Editor: Font Size ... and wait several seconds
3. The focus will be moved to the next settings item

...

It is very likely to make some error settings if the focus moved unexpectedly. I changed some font settings, this bug let me change the settings very hard and easy to make mistake.

VS Code version: Code 1.95.1 (65edc4939843c90c34d61f4ce11704f09d3e5cb6, 2024-10-31T05:14:54.222Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Remote OS version: Linux x64 5.4.241-1-tlinux4-0017.7

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

|Item|Value|
|---|---|
|CPUs|12th Gen Intel(R) Core(TM) i9-12900K (24 x 3187)|
|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>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|63.68GB (37.69GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|

|Item|Value|
|---|---|
|Remote|SSH: 9.135.147.116|
|OS|Linux x64 5.4.241-1-tlinux4-0017.7|
|CPUs|Intel(R) Xeon(R) Platinum 8255C CPU @ 2.50GHz (32 x 0)|
|Memory (System)|62.54GB (51.25GB free)|
|VM|0%|
</details><details><summary>Extensions (34)</summary>

Extension|Author (truncated)|Version
---|---|---
Bookmarks|ale|13.5.0
continue|Con|0.9.225
rust-syntax|dus|0.6.1
font-switcher|eva|4.1.0
vscode-drawio|hed|1.6.6
remote-containers|ms-|0.388.0
remote-ssh|ms-|0.115.0
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
ayu|tea|1.0.5
vim|vsc|1.28.1
rust-bundle|1Yi|1.0.0
terminal-to-here|cae|0.0.2
format-json|Cle|1.0.3
rust-syntax|dus|0.6.1
go-interface-annotations|gal|0.1.0
go|gol|0.42.1
todo-tree|Gru|0.0.226
vscode-edit-csv|jan|0.10.0
protobuf|kan|1.1.6
gitless|maa|11.7.2
rainbow-csv|mec|3.12.0
git-graph|mhu|1.30.0
debugpy|ms-|2024.12.0
python|ms-|2024.18.0
vscode-pylance|ms-|2024.11.1
cmake-tools|ms-|1.19.52
cpptools|ms-|1.22.10
cpptools-extension-pack|ms-|1.3.0
rust-analyzer|rus|0.3.2172
cody-ai|sou|1.40.2
cmake|twx|0.0.17

(3 theme extensions excluded)

</details>
<!-- generated by issue reporter -->