sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Internal edge collision and penetration of concave CollisionPolygon2D
Labels: discussion,topic:physics,needs testing,topic:2d

### Tested versions

v3.5.2.stable.mono.official [170ba337a]

### System information

WIndows 10

### Issue description

Physical bodies that should be able to slide across a CollisionPolygon2D concave suface, instead regularly catch or penetrate it at its corners.
The engine decomposes the concave polygon into convex polys, and it appears to essentially function as a set of separate shapes. Its surface is no longer continuous, instead the added internal edges seem to introduce unexpected collisions to a sliding body and in some cases can aggravate penetration.
No continuous collision or other settings found to be effective against this issue.
https://github.com/godotengine/godot/assets/7935207/70472521-9233-4817-bd65-ca1907cb7ed1

A polygon is expected to function as a singular shape with continuous surface. Decomposition the engine applies to it is expected to introduce no new collision surfaces or holes. Collision processing is expected to avoid penetration of shapes (at least in Solids + CCD) so long as the constraints acting on bodies allow that.

### Steps to reproduce

The attached project contains a scene with a concave static body, and a wedge shaped rigid body driven across its surface.
- enable Visible Collision Shapes
- run TestConcaveSliding.tscn, observe the rigid body occasionally penetrate into static body between the convex subshapes it is decomposed into, observe collisions indicated at the internal edges of the static body

### Minimal reproduction project (MRP)

[TestConcaveSliding.zip](https://github.com/godotengine/godot/files/14720657/TestConcaveSliding.zip)
TestConcaveSliding.tscn demonstrates sliding across an automatically decomposed concave shape and the penetration it results in.
TestConcaveSliding2.tscn demonstrates sliding across a concave shape with the same surface outline, but decomposed into convex subshapes in a different way that manages to prevent penetration.
Repository: rust
Issue: `with_file_name` doesn't provide checks for "path filenames"
Labels: T-libs-api,A-io

Filenames which include paths are not being treated properly by `with_file_name` in the Path library. Filenames which include ".." and other similar components are treated as part of the path. For example, consider:
```rust
use std::fs::File;
use std::path::Path;

fn main() {
    let pathtest = "test/hey.txt";
    let name = r"../gotu.txt";
    let path = Path::new(pathtest);
    let actual_path = path.with_file_name(name);

    File::create(actual_path).unwrap();
}
```
It will create "gotu.txt" at the parent directory, which could lead to potential security issues (creating files at unintended directories).

# Solutions
## Change the current behavior
Changing the implementation which will includes checks for this kind of behavior. (A very easy fix.)

## Change the documentation
Include an example, a fix or a warning about this behavior in the documentation.
Repository: material-ui
Issue: [material-ui][Transition] Add flip transition
Labels: waiting for 👍,component: transitions,package: material-ui

### Summary

I would like containers to flip, like this one:
https://github.com/acidelia/react-flippy-material-ui


### Examples

https://github.com/acidelia/react-flippy-material-ui

### Motivation

_No response_

**Search keywords**: animations
Repository: TypeScript
Issue: autocomplete workaround for string literal inside template literal stopped working since `v5.3.3`
Labels: Help Wanted,Domain: Completion Lists,Cursed?,Possible Improvement

### 🔎 Search Terms

string literal autocomplete template

### 🕗 Version & Regression Information

- This changed between versions 5.3.2 and 5.3.3



### ⏯ Playground Link

https://www.typescriptlang.org/play?ts=5.3.3#code/C4TwDgpgBAYg9nKBeKByA9AMwaqAfNLBdALgEsATXAgAyLnQBIBvAZ2ACcyA7AcygBkUZgF8RNAFASAxnG7soAIwCGHEvEQpUqIA

### 💻 Code

```ts
type Foo = '/foo' | '/foo/:id' | `/foo/${string & {}}`

const bar:Foo = ''
```


### 🙁 Actual behavior

`bar` **only** gives `/foo` as a suggestion.

### 🙂 Expected behavior

`bar` gives `/foo` and `/foo/:id` as a suggestion.

### Additional information about the issue

I understand that the autocomplete is a longer ongoing issue in combination with string literals. However there was a workaround described in (among other places): https://github.com/microsoft/TypeScript/issues/29729

This workaround (`string & {}`) still works as long as it is not inside a template literal. But stopped working inside a template literal since `v5.3.3`.
Repository: PowerToys
Issue: 当以管理员身份运行PowerPoys时，键盘管理器映射快捷键运行程序的Elevation设置成普通时不生效
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.79.0

### Installation method

WinGet

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

我映射了快捷键来启动 windwos terminal，设置了 Elevation 是普通，但它使用管理员身份来启动。
![image](https://github.com/microsoft/PowerToys/assets/73683678/b9806fd5-0a21-4979-bb67-40a7a97b6f28)


### ✔️ Expected Behavior

以普通用户身份启动windows terminal

### ❌ Actual Behavior

以管理员身份启动了windwos terminal

### Other Software

_No response_
Repository: TypeScript
Issue: Sync/Async mix return types with Generics not allowed
Labels: Bug,Help Wanted

### 🔎 Search Terms

generics, promise, inherit

### 🕗 Version & Regression Information

- Tested with 5.3 and 5.4.2


### ⏯ Playground Link

https://www.typescriptlang.org/play?#code/KYDwDg9gTgLgBAQwEYGcZQQY3pgNglFOAZRmgQHNg4BvAKDkcVXS3ipgB4AVOUGYADsAJkTRQAloIoA+ABQBKAFxxeAHzgAFKBAC2ElMB4yA3HQC+dOqEixm4tnDwEixAJ6DMpclT4gBIq5kGL70TPas2HAQAG7AUJLC1Bw8fgGicOJSsooq3GaW1uDQ8MgOUc6EcACC7p7eIdT8QhkNlNRhTGWR8LHxicnAXLzNgZno2fLKWjr6hsYFQA

### 💻 Code

```ts
export abstract class Storage {
    abstract get<T extends string>(): T | Promise<T>;
}

export abstract class SyncStorage extends Storage {
    abstract override get<T extends string>(): T;
}

export abstract class ASyncStorage extends Storage {
    abstract override get<T extends string>(): Promise<T>;
}
```


### 🙁 Actual behavior

the overridden "get" method in SyncStorage gives a type error:

```
Property 'get' in type 'SyncStorage' is not assignable to the same property in base type 'Storage'.
  Type '<T extends string>() => T' is not assignable to type '<T extends string>() => T | Promise<T>'.
    Type 'string' is not assignable to type 'T | Promise<T>'.(2416)
(method) SyncStorage.get<T extends string>(): T
```

The AsyncStorage one works as expected.

### 🙂 Expected behavior

it detects also fopr SyncStorage that it is an allowed return type of the parent class and allows it

### Additional information about the issue

In the real case T extends a type of "StorableTypes" and T is also used in a defaultValue parameter in reality, but the issue persist if I simplify it as above.
As soon as I do this without generics all works as expected, just with generics it does not
Repository: go
Issue: cmd/covdata: percent does not support -coverpkg
Labels: NeedsInvestigation

### Go version

go version go1.22.1 linux/amd64

### Output of `go env` in your module/workspace:

```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/root/.cache/go-build'
GOENV='/root/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/usr/local/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='local'
GOTOOLDIR='/usr/local/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.22.1'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='0'
GOMOD='/code/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build1985924870=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

I am trying to use `-test.gocoverdir=` to combine multiple runs of tests. But I use `-coverpkg ./...` flag because I want to have coverage calculated across sub-packages. This works well when running without coverage dir.

### What did you see happen?

I see that reported numbers by `go tool covdata percent -i=coverage` is the same as those I get when running `go test` without `-coverpkg ./...`.

### What did you expect to see?

I expected that I can pass `-coverpkg ./...` to `go tool covdata percent -i=coverage` to get the same numbers as reported by the `go test` tool when it runs (when testing on one run).
Repository: vscode
Issue: Option for sticky scroll to prioritize inner blocks
Labels: feature-request,editor-sticky-scroll

<!-- ⚠️⚠️ 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. -->

Currently sticky scroll always stick the first lines, which may make it less useful in some situations.

Consider the following case:

```html
<!DOCTYPE html>
<html>
    <body>
        <script>
            class SomeClass {
                constructor() {
                    // Long & complicated code
                    // Long & complicated code
                    // Long & complicated code
                }
            }
        </script>
    </body>
</html>
```

If we scroll to the comments with a max line count set to 3 for sticky scroll, `<html>`, `<body>` and `<script>` will stick around. However, we might not want to always stare at `<html>` whenever we write HTML, so it may be better to let `<html>` make room for inner code blocks.

| Current | Suggested alternative |
| ------- | --------------------- |
| !["<html>", "<body>" and "<script>" stuck around, as they normally would](https://github.com/microsoft/vscode/assets/110769980/192daab3-86cb-4cea-ba00-571d8b18b57d) | ![It might be better if "<script>", "class SomeClass {", and "constructor() {" stuck around instead.](https://github.com/microsoft/vscode/assets/110769980/52233861-c9d8-4297-8323-717ba5a8169f) |

This problem also applies to other languages with a complicated program structure. Adding such an option can sometimes make it more efficient to work with these languages.
Repository: next.js
Issue: Bug when using next/image and img tags 'src' inside a dynamic path and printing params 
Labels: bug,Image (next/image)

### Link to the code that reproduces this issue

https://github.com/oridori2705/next-Image-bug-report

### To Reproduce
If you put an invalid value for `src` used in the `next/image` or `img` tag within a dynamic path and output params, the invalid value is passed on.

### Problem situation
1. Create folders with dynamic paths
2. Get `params` from inside the dynamic path.
3. Use the Image component of `next/image` or `img` tag inside the dynamic path.
4. Put a variable with strange data in `src`.
5. Look at the weird data being stored in `params`

### Execution order
1. cd my-app
2. npm run dev
3. Go to that address localhost:3000/1
6. Look at the console.log output to the terminal in vsCode
7. Strange data appearing in 'params'

### Output console log
```
params : 1
RootLayout.tsx
params : worngdata2
RootLayout.tsx
params : worngdata
RootLayout.tsx
 ⨯ The requested resource isn't a valid image for /worngdata received text/html; charset=utf-8
params : sw.js
RootLayout.tsx

```
![image](https://github.com/vercel/next.js/assets/90139306/26645410-cc2d-4bc5-b069-6186e24eece9)



https://github.com/vercel/next.js/assets/90139306/ee172466-4e9e-4b7d-857b-87c727cdc2ed




### Current vs. Expected behavior

The originally existing params should continue to be output, but the src path registered to the image component of next/Image has been translated to params.

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
  Available memory (MB): 16318
  Available CPU cores: 4
Binaries:
  Node: 20.11.1
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.0-canary.38 // Latest available version is detected (14.2.0-canary.38).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

App Router, Image optimization (next/image, next/legacy/image)

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

You can find it in the GitHub repository you're currently registered in
[bug-report](https://github.com/oridori2705/next-Image-bug-report)
Repository: vscode
Issue: Font does not remain changed (Fonte não permanece alterada)
Labels: bug,confirmation-pending,workbench-fonts

Type: <b>Bug</b>

Não consigo alterar a fonte padrão para JetBrains Mono, eu instalei ela e coloquei no vscode, e após reiniciar o vscode, ela já apareceu normalmente. No entanto, depois de 2 dias ela simplesmente não aparece mais. Já coloquei ela nas configurações, verifiquei o arquivo .json e aparece lá corretamente, mas a fonte não é adotada no código. A fonte não está corrompida, posso usar ela normalmente em outros programas, mas ela não permanece no vscode.

VS Code version: Code 1.87.2 (863d2581ecda6849923a2118d93a088b0745d9d6, 2024-03-08T15:20:17.278Z)
OS version: Windows_NT x64 10.0.22631
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 7 5700U with Radeon Graphics          (16 x 1797)|
|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|
|Load (avg)|undefined|
|Memory (System)|7.35GB (2.82GB free)|
|Process Argv|--crash-reporter-id 98737bf4-bcfd-4097-ba31-bce3b1ea76bd|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (21)</summary>

Extension|Author (truncated)|Version
---|---|---
random-string-password-generator|bib|1.0.2
vscode-intelephense-client|bme|1.10.2
vscode-html-css|ecm|2.0.9
fold-unfold-all-icone|Fer|0.0.3
live-sass|gle|6.1.2
php-awesome-snippets|hak|1.1.3
rainbow-csv|mec|3.11.0
vscode-exec-node|mir|0.5.6
vscode-language-pack-pt-BR|MS-|1.87.2024031309
black-formatter|ms-|2024.0.1
debugpy|ms-|2024.2.0
python|ms-|2024.2.1
vscode-pylance|ms-|2024.3.1
material-icon-theme|PKi|4.34.0
format-html-in-php|rif|1.7.0
LiveServer|rit|5.7.9
sass-indented|syl|1.8.29
php|tal|1.0.2
errorlens|use|3.16.0
php-debug|xde|1.34.0
html-css-class-completion|Zig|1.20.0

(1 theme extensions excluded)

</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscorecescf:30445987
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:30899288
vscaat:30438848
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:30992801
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfcontrol:30979541
d34g3935:30971562
fegfb526:30981948
bg6jg535:30979843
ccp2r6:30993542
dsvsc020:30976470
pythonaic:30996667
dsvsc021:30996838

```

</details>

<!-- generated by issue reporter -->
Repository: go
Issue: runtime/debug: BuildSetting does not document DefaultGODEBUG
Labels: Documentation,NeedsFix

### Go version

go version go1.21.7 darwin/amd64

### Output of `go env` in your module/workspace:

```shell
GO111MODULE='auto'
GOARCH='amd64'
GOBIN=''
GOCACHE='/tmp/.gocache'
GOENV='/Users/rittneje/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/rittneje/go/pkg/mod'
GONOPROXY='<redacted>'
GONOSUMDB='<redacted>'
GOOS='darwin'
GOPATH='/Users/rittneje/go'
GOPRIVATE='<redacted>'
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/Users/rittneje/go1.21.7'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='local'
GOTOOLDIR='/Users/rittneje/go1.21.7/pkg/tool/darwin_amd64'
GOVCS='public:git<redacted>:git,private:off'
GOVERSION='go1.21.7'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='clang'
CXX='clang++'
CGO_ENABLED='1'
GOMOD=''
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/kf/kr7_s3xx0l12zbj3jrn082hmzy5gvy/T/go-build1761758225=/tmp/go-build -gno-record-gcc-switches -fno-common'
```


### What did you do?

Read the docs for [`runtime/debug.BuildSetting`](https://pkg.go.dev/runtime/debug#BuildSetting).

### What did you see happen?

No mention of `DefaultGODEBUG` setting.

### What did you expect to see?

I expected `DefaultGODEBUG` to be mentioned. It was spec'd as part of #56986 and was in fact implemented.

https://go.dev/play/p/ahX1MXkVAu_G
Repository: go
Issue: x/tools/gopls: inline multiple deprecated function calls at once
Labels: FeatureRequest,gopls,Tools

### gopls version

golang.org/x/tools/gopls v0.15.2

### go env

```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/stapelberg/.cache/go-build'
GOENV='/home/stapelberg/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/stapelberg/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/stapelberg/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/usr/lib/go-1.21'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/usr/lib/go-1.21/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.21.6'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/dev/null'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build1079342930=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

The situation was that I had a function that made many calls
to a deprecated function — let’s say it was ioutil.ReadFile:

```go
package main

import "io/ioutil"

func main() {
	_, _ = ioutil.ReadFile("/tmp/foo")
	_, _ = ioutil.ReadFile("/tmp/bar")
}
```


### What did you see happen?

When I place my Emacs point on ioutil.ReadFile and run `M-x eglot-code-actions`,
I do see the expected code action as the only completion:

![image](https://github.com/golang/go/assets/55506/8079415d-0227-42f0-b4b0-9e750bac900c)

But when I select multiple ioutil.ReadFile calls and run `M-x eglot-code-actions`,
I only get “Extract function” as the sole completion option:

![image](https://github.com/golang/go/assets/55506/5f6e5a06-a538-4d86-83ab-554de2e09df7)


### What did you expect to see?

Would you happen to know if inlining multiple functions at once just isn’t possible in LSP?
Or is it possible in LSP, but not possible in Emacs’s eglot?

In my case, I resorted to string replacement, because it was quicker.
Ideally, the inliner would be even quicker to reach for :) 

### Editor and settings

Emacs 29 with builtin eglot

### Logs

_No response_
Repository: flutter
Issue: SingleChildRenderObjectElement does not dispose ImageStreamCompleterHandle
Labels: a: tests,framework,f: cupertino,P2,team-framework,triaged-framework,a: leak tracking

To repro follow the steps: https://github.com/flutter/flutter/issues/141198#issuecomment-1987383965
Repository: vscode
Issue: Support GitHub-style backtick math syntax in Markdown
Labels: help wanted,feature-request,markdown

<!-- ⚠️⚠️ 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. -->

GitHub and VS Code both render math within dollar signs, but GitHub has some known bugs when rendering math like this, such as omitting curly braces. One workaround is to double up on backslashes, but VS Code interprets these as line breaks. A more general solution is to use GitHub's alternative syntax which nests backticks inside of the dollar signs, but VS Code does not support that syntax, resulting in extraneous apostrophes.

| Markdown code | GitHub render | VS Code render |
| --- | --- | --- |
| `$A = \{4, 2, 1, 3\}$` | ![GitHub plain](https://github.com/microsoft/vscode/assets/8246041/a1a7b9aa-44a7-4559-9cc4-98a8a9392bdf) | ![VS Code plain](https://github.com/microsoft/vscode/assets/8246041/50f40cf9-700b-468b-a1c2-fbdbec43ce13) |
| `$A = \\{4, 2, 1, 3\\}$` | ![GitHub with double slashes](https://github.com/microsoft/vscode/assets/8246041/e962c821-9bf4-4acf-a404-3217fafd0a22) | ![VS Code with double slashes](https://github.com/microsoft/vscode/assets/8246041/240710e7-d288-4991-849c-7bc1800e0ec3) |
| ``$`A = \{4, 2, 1, 3\}`$`` | ![GitHub with backticks](https://github.com/microsoft/vscode/assets/8246041/e962c821-9bf4-4acf-a404-3217fafd0a22) | ![VS Code with backticks](https://github.com/microsoft/vscode/assets/8246041/51931c47-a943-4808-a918-effcb780683c) |

Thus, as far as I'm aware there is currently no way to author Markdown math in VS Code such that the preview shows what GitHub will eventually render. It would be nice if VS Code supported the same backtick math syntax that GitHub supports, especially since it is already also supported by other platforms like GitLab.
Repository: vscode
Issue: Do not recommend extensions if language is set via auto detection
Labels: feature-request,languages-guessing

<!-- ⚠️⚠️ 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. -->

* Create an untitled file and type `class A`
* It auto detects language C# and prompts

![image](https://github.com/microsoft/vscode/assets/876920/601e8981-00a4-4dbd-a188-3f5645a8df09)

IMHO we should not do any extension recommendation if the language is auto detected which can be wrong.