sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: Files downloaded with torch.hub should respect umask
Labels: triaged,module: hub

### 🐛 Describe the bug

torch.hub code uses the `download_url_to_file` function to download and cache files. This function first downloads the data to a temporary file (using `NamedTemporaryFile`), then moves it into the cache directory. As a result, the file will always have 0600 permissions (this is hard-coded for files created using `NamedTemporaryFile`, and moving the file copies these permissions). As a result, umask is not respected and there is therefore no way to control the permissions of files created in the cache. This is a problem for multi-user systems that want to share the files in the torch.hub cache directory, as they will only be user-readable.

See here for discussion of a similar issue in a different Python project: https://github.com/zarr-developers/zarr-python/issues/325

### Versions

Collecting environment information...
PyTorch version: 1.11.0
Is debug build: False
CUDA used to build PyTorch: 11.5
ROCM used to build PyTorch: N/A

OS: Ubuntu 22.04 LTS (x86_64)
GCC version: (Ubuntu 11.2.0-19ubuntu1) 11.2.0
Clang version: Could not collect
CMake version: Could not collect
Libc version: glibc-2.35

Python version: 3.9.13 | packaged by conda-forge | (main, May 27 2022, 16:56:21)  [GCC 10.3.0] (64-bit runtime)
Python platform: Linux-5.15.0-40-generic-x86_64-with-glibc2.35
Is CUDA available: True
CUDA runtime version: 11.7.64
GPU models and configuration: 
GPU 0: NVIDIA GeForce GTX TITAN X
GPU 1: NVIDIA GeForce GTX TITAN X

Nvidia driver version: 515.48.07
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] numpy==1.22.4
[pip3] torch==1.11.0
[pip3] torchmetrics==0.9.2
[pip3] torchvision==0.12.0
[conda] blas                      2.114                       mkl    conda-forge
[conda] blas-devel                3.9.0            14_linux64_mkl    conda-forge
[conda] cudatoolkit               11.5.1              h59c8dcf_10    conda-forge
[conda] libblas                   3.9.0            14_linux64_mkl    conda-forge
[conda] libcblas                  3.9.0            14_linux64_mkl    conda-forge
[conda] liblapack                 3.9.0            14_linux64_mkl    conda-forge
[conda] liblapacke                3.9.0            14_linux64_mkl    conda-forge
[conda] mkl                       2022.0.1           h8d4b97c_803    conda-forge
[conda] mkl-devel                 2022.0.1           ha770c72_804    conda-forge
[conda] mkl-include               2022.0.1           h8d4b97c_803    conda-forge
[conda] numpy                     1.22.4           py39hc58783e_0    conda-forge
[conda] pytorch                   1.11.0          py3.9_cuda11.5_cudnn8.3.2_0    pytorch
[conda] pytorch-mutex             1.0                        cuda    pytorch
[conda] torchmetrics              0.9.2              pyhd8ed1ab_0    conda-forge
[conda] torchvision               0.12.0               py39_cu115    pytorch

cc @nairbv @NicolasHug @vmoens @jdsgomes
Repository: opencv
Issue: Add explicit for one argument constructor of Vec_ / Matx_
Labels: category: core,RFC

When doing the following, my code compiles but I would expect it to fail for not finding the right constructor.

```
struct MyStruct
{
  MyStruct(const cv::Vec3d& a, const cv::Vec3d& b){}
  MyStruct() = default;

  cv::Vec3b a;
  cv::Vec3b b;
};

int main()
{
  int i = 0,j = 0;
  MyStruct ms(i,j);
}

```
It works because the one-argument constructor of Vec_ is used.

Basic solution : Add the explicit keyword for the Vec_ / Matx_ one-argument constructors but it may have some bad side effects.
Repository: godot
Issue: Build in Xcode gives the error: ld: entry point (_main) undefined. for architecture arm64
Labels: platform:ios,topic:buildsystem,documentation

### Godot version

v3.4.4.stable.official [419e713a2]

### System information

MacBook Air (M1, 2020), MacOS Monterey 12.4

### Issue description

When I Try to build and run the simulation in Xcode it keep me showing this error: `ld: entry point (_main) undefined. for architecture arm64`

Viewing others Issues and people that happened something similar, I made the conclusion that the problem may be in the Godot Export Templates, but Im not sure if this is the case, also, the Xcode log gives me this warning: 

`ld: warning: ignoring file /Users/personale/Library/Developer/Xcode/DerivedData/GELATO_ESPRESSO_GAME_1.1.0-gdmnsorzziyfncbhrzowwqvzlbus/Build/Products/Release-iphonesimulator/libgodot.a, building for iOS Simulator-arm64 but attempting to link with file built for iOS Simulator-x86_64`

**Note that last line**: building for iOS Simulator-arm64 but attempting to link with file built for iOS Simulator-x86_64

I supused that the problem is in that file, so it can be a problem with the Godot export?

So, my hypothesis is that Godot is exporting the project with a file configured to x86, but not to armv64, giving this error, the Mac that Im using for build the project has an Apple M1, I think that if I try to build it in a Mac with an Intel processor it may work.

So, somebody can help me with this problem? Is this a problem that can be solved in the Xcode configuration? or is a problem with the Godot Export Templates?


### Steps to reproduce

1. Export you project for iOS with the following configuration: 
![image](https://user-images.githubusercontent.com/74997202/178389874-61ecb4ae-1924-49fc-9ab3-5491445a3695.png)
![image](https://user-images.githubusercontent.com/74997202/178390140-c48f8a2e-3eaf-423b-bcf5-1f30617d9f92.png)

2. Import the project to Xcode

3. Build the project


### Minimal reproduction project

_No response_
Repository: godot
Issue: Vulkan: VoxelGI displays outside the extents when its extents are not uniform
Labels: bug,topic:rendering,confirmed,topic:3d

### Godot version

v4.0.alpha11.official [afdae67cc]

### System information

Windows 11, Vulkan, Nvidia 1070 GTX

### Issue description

Geometry outside the extents of a VoxelGI can be incorrectly lit by bounced light, if the VoxelGI extents are not a perfect uniform cube (all dimensions are equal).

### Steps to reproduce

Using the attached reproduction project, bake the VoxelGI, you will see all the red light is contained with the VoxelGI extents.  Then decrease the Z extent from 6m to 5m, bake again, and you will see red lighting leaking from the VoxelGI, along the +Z axis, by about 1m.

### Minimal reproduction project

[VoxelGILeak.zip](https://github.com/godotengine/godot/files/9088744/VoxelGILeak.zip)
Repository: terminal
Issue: Support the Alt+X keybinding to toggle between an Unicode character and its hex encoding
Labels: Issue-Feature,Area-Input,Product-Terminal,Area-i18n

# Description of the new feature/enhancement

As suggested by @MurraySargent:
A number of Microsoft applications (e.g. Word, Notepad) allow you to press Alt+X to switch between a Unicode character and its hex encoding. For instance you can enter a hex number like "222b", press Alt+X and get "∫". Pressing Alt+X again, will turn it back into "222b".

This appears to be a useful alternative to the old Alt+Numpad input, which fails to work on keyboards without numpad. However I'm unsure whether implementing this feature is trivially possible without running into edge cases (it requires us to erase characters previously sent to the shell).

# Proposed technical implementation details (optional)

RichEdit's `CTxtRange::HexToUnicode()`.
Repository: go
Issue: debug/dwarf: incorrect runtime.newproc DIE in .zdebug_info
Labels: NeedsInvestigation,compiler/runtime

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.18.3 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN="/home/gray//bin"
GOCACHE="/home/gray/.cache/go-build"
GOENV="/home/gray/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/gray/pkg/mod"
GONOPROXY="git.insea.io"
GONOSUMDB="git.insea.io"
GOOS="linux"
GOPATH="/home/gray/"
GOPRIVATE="git.insea.io"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.18.3"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/gray/src/proving_grounds/go_hello_world/go.mod"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2957214737=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

Build a hello world:

```go
package main

import "fmt"

func main() {
    fmt.Println("hello world")
}
```

Then check the `runtime.newproc` entry in .zdebug_info

```shell
$ objdump -Wi ./go_hello_world | grep 'runtime.newproc$' -A2
    <4196c>   DW_AT_name        : runtime.newproc
    <4197c>   DW_AT_low_pc      : 0x43a9a0
    <41984>   DW_AT_high_pc     : 0x43aa19
--
    <524a7>   DW_AT_name        : runtime.newproc
    <524b7>   DW_AT_low_pc      : 0x45cea0
    <524bf>   DW_AT_high_pc     : 0x45cecf
```

There are 2 different DIE for `runtime.newproc`, but only the first one is correct.

The second entry is actually for `runtime.newproc.abi0`, and we can tell it from the .symtab, but the dwarf emitter made mistakes:

```
$ nm ./go_hello_world | grep runtime.newproc
000000000043a9a0 T runtime.newproc
000000000043aaa0 T runtime.newproc1
000000000045cea0 T runtime.newproc.abi0
000000000043aa20 T runtime.newproc.func1
000000000054ef1c B runtime.newprocs
```

### What did you expect to see?

I expected to see the only one entry for `runtime.newproc`.

### What did you see instead?

I saw 2 different entries for `runtime.newproc`, in which one entry should have been `runtime.newproc.abi0`.
Repository: pytorch
Issue: [Prims+NvFuser] Non-fusible ops Tracker
Labels: triaged,module: nvfuser

Following is the complete list of ops that appear in the torchbench + huggingface + TIMM models, but are not included in the nvFuser fusion group.

They are not included due to one (or more) of the following reasons: 
1. nvFuser backend does not support this op
2. aten2aten missing 
3. aten2prim ref missing 
4. nvfuser_impl missing for prims op
5. not included in NvFuserOperatorSupport dict

Tracking is moved here: https://docs.google.com/spreadsheets/d/1kmFvpIQ42XB4okN2WYrLX7D6svkRhbJX_iCFqM231YQ/edit#gid=0

  | Occurance
-- | --
aten.view.default' | 14567
aten.t.default' | 10085
aten.to.dtype' | 8595
aten.unsqueeze.default' | 6639
aten.permute.default' | 5395
aten.mm.default' | 4915
aten._unsafe_view.default' | 3585
aten.clone.default' | 2890
aten.new_zeros.default' | 2408
aten.bmm.default' | 2312
aten.reshape.default' | 1866
aten.expand.default' | 1674
aten.addmm.default' | 1423
aten.convolution.default' | 1112
aten.convolution_backward.default' | 1045
aten.slice.Tensor' | 1030
aten.native_layer_norm_backward.default' | 568
aten.mean.dim' | 436
aten.amax.default' | 362
aten.squeeze.dim' | 260
aten.cat.default' | 205
aten.narrow.default' | 192
aten.var.dim' | 114
aten.empty_like.default' | 103
aten._to_copy.default' | 75
aten.where.ScalarSelf' | 73
aten.select.int' | 70
aten.embedding_dense_backward.default' | 65
aten.zero.default' | 55
aten.fill.Scalar' | 49
aten.index_select.default' | 48
aten.select_scatter.default' | 41
aten.hardtanh.default' | 35
aten.max_pool2d_with_indices.default' | 35
aten.reflection_pad2d.default' | 31
aten.max_pool2d_with_indices_backward.default' | 28
aten.reflection_pad2d_backward.default' | 28
aten.avg_pool2d.default' | 23
aten.constant_pad_nd.default' | 21
aten.upsample_bilinear2d.vec' | 18
aten.avg_pool2d_backward.default' | 13
aten.col2im.default' | 12
aten.im2col.default' | 12
aten.index.Tensor' | 11
aten.mean.default' | 10
aten.slice_scatter.default' | 9
aten._embedding_bag.default' | 8
aten.upsample_bilinear2d_backward.vec' | 8
aten.grid_sampler_2d.default' | 6
aten.stack.default' | 6
aten._adaptive_avg_pool2d_backward.default' | 2
aten._adaptive_avg_pool2d.default' | 2
aten.any.default' | 1
aten.gather.default' | 1
aten.new_empty.default' | 1
aten.repeat.default' | 1
aten.scatter_add.default' | 1
Repository: neovim
Issue: `:language time` doesn't give an error for invalid language on OpenBSD
Labels: bug,test,platform:bsd

### Neovim version (nvim -v)

N/A

### Vim (not Nvim) behaves the same?

N/A

### Operating system/version

sourcehut CI openbsd/latest

### Terminal name/version

N/A

### $TERM environment variable

N/A

### Installation

N/A

### How to reproduce the issue

Run oldtests on OpenBSD

### Expected behavior

Tests pass

### Actual behavior

Test failure is (<https://builds.sr.ht/~jmk/job/799797>):
```
Failures: 
	From test_excmd.vim:
	Found errors in Test_language_cmd():
	function RunTheTest[40]..Test_language_cmd line 3: command did not fail: language ctype non_existing_lang
	function RunTheTest[40]..Test_language_cmd line 4: command did not fail: language time non_existing_lang
```
Repository: svelte
Issue: Transition function does not run on destroy
Labels: transition/animation

### Describe the bug

[`transition:fn`](https://svelte.dev/docs#template-syntax-element-directives-transition-fn) does not run when an element gets destroyed.

If the computed style of an element changes between creation and destruction, the transition can break.

### Reproduction

In this [REPL](https://svelte.dev/repl/9e1a743a5f41430fb22f2e0caef79c20?version=3.49.0)

- Click on the lower box (`2`)
- Click on the upper box (`1`)
- Click on the upper box (`2`)

Transition functions of boxes `3` and `0` run on creation, but not on destruction.

```shell
"clicked 2"
"0 will be destroyed"
"3 will be created"
"0 css is calculated"
"3 css is calculated"

"clicked 1"
"3 will be destroyed"
"0 will be created"
# Missing "3 css is calculated"
"0 css is calculated"

"clicked 2"
"0 will be destroyed"
"3 will be created"
# Missing "0 css is calculated"
"3 css is calculated"
```

---

In this [REPL](https://svelte.dev/repl/1eb9053c3bcc4e6a8ce184ef6240c284?version=3.49.0)

- Click on the right box (`2`)
- Change the Result width
- Click on the left box (`1`)

Destruction transition of box `3` breaks only after the viewport is resized.

https://user-images.githubusercontent.com/47051820/178408233-6d8a25b9-9d2f-445f-b082-fa1f382219d3.mp4

### Logs

_No response_

### System Info

```shell
System:
  OS: Windows 10 10.0.19044
Browsers:
  Chromium (103.0.1264.49)
```


### Severity

annoyance
Repository: vscode
Issue: feedback ui/ux issues
Labels: bug,issue-reporter


Issue Type: <b>Bug</b>

- "tweet feedback" window disappears if you move the mouse slightly off the button in the status bar, even while typing in it. it is a terrible ux.

- this "issue reporter" window that opens when clicking "submit a bug" is not listed in taskbar or alt-tab so if you switch away from it while typing in it, you may think it disappeared too.

VS Code version: Code 1.68.1 (30d9c6cd9483b2cc586687151bcbcd635f373630, 2022-06-14T12:48:58.283Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No

<!-- generated by issue reporter -->
Repository: next.js
Issue: output: "standalone" not working when using .cjs as config file extension.
Labels: bug,linear: next

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

    Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 21.4.0: Fri Mar 18 00:46:32 PDT 2022; root:xnu-8020.101.4~15/RELEASE_ARM64_T6000
    Binaries:
      Node: 16.15.0
      npm: 8.5.5
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 12.2.2
      eslint-config-next: 12.1.4
      react: 18.0.0
      react-dom: 18.0.0

### What browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_

### Describe the Bug

The option `output: "standalone"` in the `next.config.js` file is ignored when using `next.config.cjs` (note: `.cjs`) as file extension.

### Expected Behavior

`output: "standalone"` should work in both `.js` and `.cjs` files

### Link to reproduction

N/A

### To Reproduce

N/A
Repository: flutter
Issue: [Proposal]Height of Text Widget should be a double instead of integer
Labels: framework,engine,a: typography,c: proposal,P2,team-engine,triaged-engine

<img width="200" alt="image" src="https://user-images.githubusercontent.com/107851852/178426785-e1b71780-ac69-45d6-9021-83387f64df20.png">
<img width="200" alt="image" src="https://user-images.githubusercontent.com/107851852/178430224-7663ab77-87c3-4c05-92ce-e8140493caf8.png">

If there are a lot of Text Widgets one below another, there is a space at the bottom.
The height of Text Widget is rounded to 10 and is not 10.4.
I want to make Container height and font size dependent on the screen width, so I can't have a rounded Text Widget height.
The height of the Text Widget must be of type double. Then there will be no space  at the bottom.

```dart
Material(
  child: Row(
    children: [SingleChildScrollView(
      child: Column(
        children: [Container(
          color: Colors.red,
          height: 1040,
          width: 100,
          child: Column(
            children: [for (var a = 0; a < 100; a++) Text(
              'TEST',
              style: TextStyle(
                fontSize: 10.4,
                height: 1))]))]))]))
```
Repository: go
Issue: gollvm: multiple definition of 'runtime.nanotime..f'
Labels: NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
-->
As shown in the sample code,  since Nanotime is declared in both package main and packagea(using: //go:linkname Nanotime runtime.nanotime), and package packagea is imported to package main.
gofrontend creates the function descriptor with the same name "runtime.nanotime..f" for Nanotime in both packages main and packagea, resulting in a multiple definition error during the link phase.
### What version of Go are you using (`go version`)?
gollvm master
<pre>
$ go version
go version unknown linux/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env

</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->
The issue may be reproduced with the following sample:

go build linkname.go

File linkname.go
```go
package main
  
import (
    "fmt"
    "linkname/packagea"
    _ "unsafe"
)

//go:linkname Nanotime runtime.nanotime
func Nanotime() int64

func main() {
    fmt.Println(Nanotime())
    fmt.Println(packagea.Nanotime)
}
```

File packagea/a.go
```go
package packagea
  
import (
        _ "unsafe"
)

//go:linkname Nanotime runtime.nanotime
func Nanotime() int64
```

### What did you expect to see?
No error, successful build.

### What did you see instead?
```bash
[root@kwephis525702 test]# go build linkname.go 
# command-line-arguments
/usr/bin/ld.gold: error: /root/.cache/go-build/72/72a31748b9a7e4660f3fbe9b02046db2b83d204da0b133c508593d4b82ac82b3-d(_go_.o): multiple definition of 'runtime.nanotime..f'
/usr/bin/ld.gold: $WORK/b001/_pkg_.a(_go_.o): previous definition here
```
Repository: godot
Issue: Shaders : Global uniform declaration breaks loading the project
Labels: bug,topic:editor,topic:shaders

### Godot version

4.11 alpha

### System information

Windows 11

### Issue description

 If I declare a global uniform in the shader script, project crashes on next loading; 
WORKAROUND: deleting the declaration with notepad directly in .tres file before launch and then retyping it again, once loaded. [they work fine during the session (yes, I added global in project settings)]

### Steps to reproduce

```
shader_type canvas_item;
global uniform float g;

void fragment(){
	vec4 color = texture(TEXTURE,UV);
	color.a-=g;
	COLOR = color;
}
```
2. Add float global uniform in project settings, so there is no error spotted by the engine.
3. close and reopen the project.


### Minimal reproduction project

_No response_
Repository: material-ui
Issue: [Autocomplete] slow with huge number of items (1mio)
Labels: performance,component: autocomplete

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

We have a huge autocomplete (1mio items). 

Performance is slow even though we have both used virtualization and a limit on filter options.  It looks like an internal algo is going over the whole list even though only a few items are eventually going to be visible. 

You can check performance on the virtualization demo changed with a larger amount of items and a limit size 

https://codesandbox.io/s/virtualize-demo-material-ui-forked-ri9fo4?file=/demo.tsx



### Expected behavior 🤔

Faster :-)

### Steps to reproduce 🕹

_No response_

### Context 🔦

_No response_

### Your environment 🌎

Order ID 💳 
#19458
Repository: vscode
Issue: find and replace works poorly in notebooks
Labels: bug,papercut :drop_of_blood:,notebook-find


Issue Type: <b>Bug</b>

when searching I can't get it to start in the block I'm at so I have to start from the top. Then when I replace one it loses track of where I am and I can't just do a replace on the next without stepping to it again

VS Code version: Code 1.68.1 (30d9c6cd9483b2cc586687151bcbcd635f373630, 2022-06-14T12:48:58.283Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-8365U CPU @ 1.60GHz (8 x 1896)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>oop_rasterization: enabled<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_renderer: enabled_on<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|15.81GB (6.51GB free)|
|Process Argv|--crash-reporter-id e605730f-f6a1-46f1-876b-660e6485fa1e|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (6)</summary>

Extension|Author (truncated)|Version
---|---|---
python|ms-|2022.10.0
vscode-pylance|ms-|2022.7.20
jupyter|ms-|2022.5.1001601848
jupyter-keymap|ms-|1.0.0
jupyter-renderers|ms-|1.0.8
powershell|ms-|2022.6.3


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vscscmwlcmt:30465135
cppdebug:30492333
vscaac:30438847
vsclangdf:30486550

```

</details>

<!-- generated by issue reporter -->