sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Add debug window context menu contribution points
Labels: feature-request,debug

Forking https://github.com/microsoft/vscode/issues/200880 into this issue for context menus in the debug view.

https://github.com/microsoft/vscode/pull/212501
Repository: PowerToys
Issue: Abysmal performance from SVG Thumbnail Provider
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.83.0

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

File Explorer: Thumbnail preview

### Steps to reproduce

- Clear your cached thumbnails using Windows' Disk Cleanup
- Open a folder with a large amount of SVG files (>100)
- Observe the speed of thumbnail creation

My bug report log:  [PowerToysReport_2024-08-29-18-54-31.zip](https://github.com/user-attachments/files/16806487/PowerToysReport_2024-08-29-18-54-31.zip)

### ✔️ Expected Behavior

Thumbnails should be rendered in less than 500 milliseconds each.
In the video bellow, [SvgSee](https://github.com/tibold/svg-explorer-extension) is used to make the thumbnails. My computer uses a Intel Core i5-3330; NVIDIA GeForce GTX 650 Ti; 16 GB DDR3-1333 SDRAM; and Windows 10 Enterprise v10.0.19045.4780 installed on a SATA SSD.

https://github.com/user-attachments/assets/74a4690a-bc5a-470c-9c96-e65f08cb2326

### ❌ Actual Behavior

- Thumbnails takes ~2 seconds to render.
- A `msedgewebview2.exe` process is created for every file.
- Many `PowerToys.SvgThumbnailProvider.exe` processes are created.
- There are unnecessary network activity, `msedgewebview2.exe` calls home every time a thumbnail is created. (turning the network off doesn't seem to have any effect)
- Windows Defender is used but I am uncertain of it's impact.

In this video, PowerToys is used to render the thumbnails. Note the time it takes to render all the files.

https://github.com/user-attachments/assets/f6221f7b-dd6f-47fd-9eeb-0d0765d859a9

### Other Software

_No response_
Repository: deno
Issue: `fmt` Breaks GitHub Markdown's Callout Syntax
Labels: needs info,deno fmt,needs triage

**Describe the bug**

When running `deno fmt` against Markdown files it will move the start of the callout to the first line and then spread `>` block quotes over multiple lines if they are of a certain length.

``` example.md
> [!NOTE] "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do 
> eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim > veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea..."
```

Which renders on GitHub as:

> [!NOTE] "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do 
> eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim > veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea..."

**Steps to Reproduce**

1. Create a Markdown files.
2. Add a callout using [correct syntax](https://github.com/orgs/community/discussions/16925).
3. Run `deno fmt file.md`.
4. See incorrect formatting.

**Expected behavior**

What should happen in order for the syntax to match up to GFM and correctly render the callout on GitHub:

``` correct.md
> [!NOTE]
> "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea..."
```

Which renders on GitHub as:

> [!NOTE]
> "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea..."

**Environment**

<!-- please complete the following information -->

- OS: macOS Version 15.0 Beta (24A5309e)
- deno version: deno 1.46.1
- std version: whichever is bundled with `deno`
Repository: pytorch
Issue: enhanced debugging prints in torch.distributed
Labels: oncall: distributed,triaged

### 🚀 The feature, motivation and pitch

It's hard to debug nccl timeout issue at a2a op but enhanced debugging prints can make life a bit better.

In `distributed/distributed_c10d.py`
```
    work = group.alltoall_base(
        output, input, output_split_sizes, input_split_sizes, opts
    )
```

I can definitely insert my own adhoc print here to debug timeout and maybe more.  I wonder if PT-D team can initiate a centralized design to enhance debug prints.

### Alternatives

_No response_

### Additional context

_No response_

cc @XilunWu @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o
Repository: TypeScript
Issue: TS2454 Variable is used before being assigned with strictNullChecks when variable is clearly assigned but can be undefined
Labels: Bug

### 🔎 Search Terms

Variable is used before being assigned TS2454 TS(2454) undefined strictNullChecks

### 🕗 Version & Regression Information

- This happens at least since version 3.7.5 (tested in the playground)
- This is the behavior in every version I tried, and I reviewed the FAQ


### ⏯ Playground Link

https://www.typescriptlang.org/play/?#code/DYUwLgBGIM6QvBArgOwCYgGYEsUjQNwBQR0cEiA5JRAIYwRwBOuA5hAD7Lpa77GlYYAPwA6UClZgAFgSA

### 💻 Code

```ts
let test = undefined;

test = '' as string | undefined;

test?.length; // Variable 'test' is used before being assigned.
```


### 🙁 Actual behavior

Typescript throws an error complaining about `test` being used before being assigned but it's clearly assigned to undefined and then to ''.

Mine is a very simplicistic problem, but the same issues happens if a replace `''` with a call to a function.

### 🙂 Expected behavior

Typescript should assign the type `string | undefined` to the variable `test` and let me use it.

### Additional information about the issue

_No response_
Repository: PowerToys
Issue: Display activations codes/product keys/PC serial number
Labels: Needs-Triage

### Description of the new feature / enhancement

A tool that lists all the microsoft product keys installed on your PC, and additionally the PC serial number if that's possible.
For exemple :  Office (Word, Powerpoint, Excel, Project, Viso, etc.) product keys, and Windows 11 activation key. Such tools exists, and are available from the Store, but can they be trusted ? 

### Scenario when this would be used?

1. For backup purposes
2. Before a system reinstallation
3. Before a computer hardware replacement
4. etc.

### Supporting information

Several techniques exists, but are difficult to use for a non tech person (eg. open a cmd in admin mode and type Get-WmiObject –query 'select * from SoftwareLicensingService...)
Repository: godot
Issue: Editor cannot assign custom node to member in C# script when using [Tool] annotation
Labels: enhancement,discussion,topic:editor,topic:dotnet

### Tested versions

v4.3.stable.mono.official [77dcf97d8]

### System information

Godot v4.3.stable.mono - Windows 10.0.22631 - Vulkan (Forward+) - integrated AMD Radeon(TM) Graphics (Advanced Micro Devices, Inc.; 31.0.12029.10015) - AMD Ryzen 9 5900HX with Radeon Graphics (16 Threads)

### Issue description

When assigning a custom node to an [Export] member in a C# script, a cast error occurs because the item is assigned with the super type instead of the actual custom node type. This issue only occurs when the script is executed in the editor using the [Tool] annotation. When the project runs normally, the types are assigned correctly.
```
/root/godot/modules/mono/glue/GodotSharp/GodotSharp/Core/NativeInterop/ExceptionUtils.cs:113 - System.InvalidCastException: Unable to cast object of type 'Godot.Node' to type 'CustomNode'.
     at class_error.FailureNode.SetGodotClassPropertyValue(godot_string_name& name, godot_variant& value) in C:\Mateus\Godot Engine\Projetos\class_error\Godot.SourceGenerators\Godot.SourceGenerators.ScriptPropertiesGenerator\class_error.FailureNode_ScriptProperties.generated.cs:line 27
     at Godot.Bridge.CSharpInstanceBridge.Set(IntPtr godotObjectGCHandle, godot_string_name* name, godot_variant* value) in /root/godot/modules/mono/glue/GodotSharp/GodotSharp/Core/Bridge/CSharpInstanceBridge.cs:line 57
```

### Steps to reproduce

**Steps to reproduce:**
1. Create a custom node in C#.
2. Create a new scene and attach a C# script to a node in the scene.
3. Annotate the C# script with [Tool] and use the [Export] attribute to specify the custom node type for a member.
4. In the editor, try to assign the custom node to the exported member.

**Expected behavior:** The custom node should be correctly assigned to the member of its specific type.
**Actual behavior:** A cast error occurs because the assigned item type is its super type rather than the specific custom node type.
**Note:** This issue only occurs when the script is executed in the editor. When the project runs normally, the node types are assigned correctly.

### Minimal reproduction project (MRP)

[mrp.zip](https://github.com/user-attachments/files/16808411/class_error.zip)
In the "failure_scene.tscn", there is a custom node property that cannot be assigned in the editor.
Repository: rust
Issue: Next-gen Trait Solver does not implement Generic Const Expressions
Labels: T-compiler,C-bug,A-const-generics,F-generic_const_exprs,T-types,WG-trait-system-refactor,requires-incomplete-features

I was fluffing around with different generic stuff and ended up enabling the Next-gen solver, where I realized that it looked like Generic Const Expressions just don't work at all.

This code seems to work fine with the default trait solver, but when you enable the `-Znext-solver` flag, it throws a normalization error.

```rust
#![feature(generic_const_exprs)]
pub struct Vec<T, const N: usize>
where
    [T; N * N]: Sized,
{
    packed: [T; N * N],
}
```

I understand this is all very unstable stuff, but thought it was still probably slightly unintended behavior at the least.

### Meta
`rustc --version --verbose`:
```
rustc 1.82.0-nightly (100fde524 2024-08-28)
binary: rustc
commit-hash: 100fde5246bf56f22fb5cc85374dd841296fce0e
commit-date: 2024-08-28
host: x86_64-unknown-linux-gnu
release: 1.82.0-nightly
LLVM version: 19.1.0
```

<details><summary>Backtrace</summary>
<p>

```
error[E0284]: type annotations needed: cannot normalize `Vec<T, N>::packed::{constant#0}`
 --> src/main.rs:6:13
  |
6 |     packed: [T; N * N],
  |             ^^^^^^^^^^ cannot normalize `Vec<T, N>::packed::{constant#0}`
```

</p>
</details>
Repository: storybook
Issue: [Bug]: Addon Does Not Contribute Addons
Labels: bug,needs triage

### Describe the bug

I cloned the Addon Kit repo (moreso added a copy of it into our monorepo)
I followed the setup from Addon Essentials, primarily being that the root `index.ts` exports an `addons` function which returns an array of addons.
When we run storybook with our custom addon (based on Addon Kit), none of the addons contributed by our addon are loaded.
Further, adding any amount of logging (or throws) in the index.ts does not produce any result. Therefore, my suspicion is that storybook does not even load the index.ts

### Reproduction link

In progress

### Reproduction steps

I know this bug report is half assed, I'm sorry (truly). I've spent all day debugging issues related to storybook not loading our SSL certificates correctly --> so I'm a little exhausted right now.

I'll work on creating a repro, but will also likely not be on stackblitz because I don't know how to create one with a custom addon. 

Further, the lack of documentation for how to write good addons is a little frustrating. Even the Addon Kit example does not work with latest storybook out of the box (at least not for me).

I really just wanted to get this bug report filed as a placeholder. If any of this makes sense to someone, great! Otherwise please feel free to ignore until I have a clear repro.

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.5
    CPU: (10) arm64 Apple M1 Max
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.12.2 - ~/.nvm/versions/node/v20.12.2/bin/node
    Yarn: 4.4.0 - ~/.nvm/versions/node/v20.12.2/bin/yarn <----- active
    npm: 10.5.0 - ~/.nvm/versions/node/v20.12.2/bin/npm
    pnpm: 9.1.1 - ~/.nvm/versions/node/v20.12.2/bin/pnpm
  Browsers:
    Chrome: 128.0.6613.85
    Safari: 17.5
```


### Additional context

_No response_
Repository: pytorch
Issue: DISABLED test_garbage_collect_expandable (__main__.TestCudaMallocAsync)
Labels: module: cuda,triaged,module: flaky-tests,skipped

Platforms: linux

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_garbage_collect_expandable&suite=TestCudaMallocAsync&limit=100) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/29448105511).

Over the past 3 hours, it has been determined flaky in 30 workflow(s) with 90 failures and 30 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_garbage_collect_expandable`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.



<details><summary>Sample error message</summary>

```
Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test/test_cuda.py", line 4146, in test_garbage_collect_expandable
    a = alloc(40)
  File "/var/lib/jenkins/workspace/test/test_cuda.py", line 4141, in alloc
    return torch.ones(n * mb, dtype=torch.int8, device="cuda")
torch.OutOfMemoryError: CUDA out of memory. Tried to allocate 40.00 MiB. GPU 0 has a total capacity of 21.98 GiB of which 20.36 GiB is free. Process 329937 has 248.00 MiB memory in use. Process 329975 has 358.00 MiB memory in use. Process 330076 has 248.00 MiB memory in use. Process 330111 has 520.00 MiB memory in use. Process 331287 has 248.00 MiB memory in use. 120.00 MiB allowed; Of the allocated memory 50.00 MiB is allocated by PyTorch, with 14.00 MiB allocated in private pools (e.g., CUDA Graphs), and 90.00 MiB is reserved by PyTorch but unallocated. If reserved but unallocated memory is large try setting PYTORCH_CUDA_ALLOC_CONF=expandable_segments:True to avoid fragmentation.  See documentation for Memory Management  (https://pytorch.org/docs/stable/notes/cuda.html#environment-variables)

To execute this test, run the following from the base repo dir:
    python test/test_cuda.py TestCudaMallocAsync.test_garbage_collect_expandable

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0
```

</details>


Test file path: `test_cuda.py`

cc @ptrblck @msaroufim @clee2000
Repository: PowerToys
Issue: Change File Icon
Labels: Needs-Triage

### Description of the new feature / enhancement

A tool to change file association icons.

### Scenario when this would be used?

I want to make `.code-workspace` icons more prominent, changing them from this:

![image](https://github.com/user-attachments/assets/1316669d-aea8-4672-a7de-24b0f4c2a403)

to this:

![image](https://github.com/user-attachments/assets/3f143a44-00c3-4f5b-ba16-62b9cd1fa8da)

Basically, an editor for those registry entries:

![image](https://github.com/user-attachments/assets/258bad15-4f91-4526-8cbc-99e6e5509b8d)
Repository: terminal
Issue: Incorrect Korean translation
Labels: Issue-Bug,Product-Terminal,In-PR,Area-Localization

### Windows Terminal version

v1.21.2361.0

### Windows build number

_No response_

### Other Software

_No response_

### Steps to reproduce

Browse this repository.

### Expected Behavior

1.  `<value>파일에서 설정을 로드하지 못했습니다. 후행 쉼표를 포함하여 구문 오류가 있는지 확인합니다.</value>`
2.  `<value>새 탭 만들기</value> `
3. ` <value>읽기 전용 터미널을 닫으려고 합니다. 계속하시겠습니까?</value> `
4. `<value>진홍</value>`

### Actual Behavior

1. https://github.com/microsoft/terminal/blob/93d592bb4156e85f66f34a57ee7f707cc7ba0f15/src/cascadia/TerminalApp/Resources/ko-KR/Resources.resw#L121
2. https://github.com/microsoft/terminal/blob/17a55da0f9889aafd84df024299982e7b94f5482/src/cascadia/TerminalApp/Resources/ko-KR/Resources.resw#L322
3. https://github.com/microsoft/terminal/blob/17a55da0f9889aafd84df024299982e7b94f5482/src/cascadia/TerminalApp/Resources/ko-KR/Resources.resw#L527
4. https://github.com/microsoft/terminal/blob/93d592bb4156e85f66f34a57ee7f707cc7ba0f15/src/cascadia/TerminalApp/Resources/ko-KR/Resources.resw#L619

String ID | Current | Suggestion
--------- | ------- | ----------
InitialJsonParseErrorText | 파일에서 설정을 로드 하지 못했습니다. 후행 쉼표를 포함 하 여 구문 오류가 있는지 확인 합니다. | 파일에서 설정을 로드하지 못했습니다. 후행 쉼표를 포함하여 구문 오류가 있는지 확인합니다.
CmdNewTabDesc | 새 작업 만들기 | 새 탭 만들기
CloseReadOnlyDialog.Content | 읽기 전용 터미널을 닫으려고 합니다. 계속하시겠어요? | 읽기 전용 터미널을 닫으려고 합니다. 계속하시겠습니까?
CrimsonColorButton.[using:Windows.UI.Xaml.Controls]ToolTipService.ToolTip | 심홍 | 진홍
Repository: TypeScript
Issue: Type PermissionName for Permission API doesn't contain microphone and camera devices
Labels: Needs Investigation

### 🔍 Search Terms

microphone, camera, device, permission, state, API, navigator

### ✅ Viability Checklist

- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [X] This wouldn't change the runtime behavior of existing JavaScript code
- [X] This could be implemented without emitting different JS based on the types of the expressions
- [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

In both files, webworker.generated.d.ts and dom.generated.d.ts in line 9361 and 27992.

The modification would be add two terms in the type PermissionName. 'camera' and 'microphone' to check access in both devices

### 📃 Motivating Example

```
  const checkForPermission = (type: PermissionName) => {
    navigator.permissions
      .query({
        name: type,
      })
      .then(permissionStatus => {
        // Will be 'granted', 'denied' or 'prompt':
        console.log(permissionStatus);
        // permissionStatus.state = 'granted'
        // Listen for changes to the permission state
        permissionStatus.onchange = () => {
          console.log(permissionStatus.state);
        };
      });
  };

  checkForPermission('microphone');
  checkForPermission('camera');
```


**Expected behavior:**
'microphone' and 'camera' should be valid types for PermissionName type.

**Actual behavior:**
'microphone' and 'camera' are not valid types for PermissionName type.
Typescript is showing error:
Argument of type '"microphone"' is not assignable to parameter of type 'PermissionName'.

### 💻 Use Cases

1. What do you want to use this for?
Check if camera or microphone are enabled/disabled

3. What shortcomings exist with current approaches?
To type the promise from navigator.permission in typescript, we have to add a inclusion on type PermissionName like: { PermissionName } & { name: 'camera' | 'microphone' }.

5. What workarounds are you using in the meantime?
I'm using it: { PermissionName } & { name: 'camera' | 'microphone' }
Repository: pytorch
Issue: torch.onnx.verification.verify() lacks the option to pass in SessionOptions - crucial for custom upset support
Labels: module: onnx,triaged,onnx-needs-info

### 🚀 The feature, motivation and pitch

Thank you for making torch.onnx.verification.verify()! It really helps!
It does not work, however, for models that use onnx_extensions and custom operations. 
To make them work, we simply need to add an option to pass SessionOptions to  torch.onnx.verification.verify - and from there to here: 
https://github.com/pytorch/pytorch/blob/cf11fc0dcbb9c907cf6e851109b92f4157e445c9/torch/onnx/verification.py#L177

Best regards,
-Boris.

### Alternatives

_No response_

### Additional context

_No response_
Repository: next.js
Issue: Third-party script synchronous loading Hydration problem
Labels: bug,Script (next/script)

### Link to the code that reproduces this issue

https://github.com/yanqc1996/GD-Next

### To Reproduce

Description of the problem encountered: I have to rely on an external third-party js in the project to perform a/b testing on the page, in which we may have a test for page diversion, which forces me to divert before loading the page content (to prevent users from seeing page a before page b), which also forces me to load this js script synchronously to block page rendering, so next/script does not apply to me because there is no synchronization option. I use native <script> loading (eslint will report an error when srcipt is loaded synchronously, but this can be prohibited by custom rules)

The deployment address of vercel is: https://gd-next-un88.vercel.app/. When you open the console, you can see that there are many Hydration errors in the right window.

When in official use, these errors will even affect the rendering of the page. I must trigger a click before rendering other things. For example, the test page https://vibe-portal-rik-vibeus.vercel.app/products/vibe-smart-whiteboard-s1/, you can try to open the page without a trace, and you will find that the loading of home page pictures/videos will be stuck, and can only be loaded after triggering a click

I don’t think this is a Next.js problem. I just want to ask if there is a solution that allows me to load only a synchronous blocking rendering js script on the client?

If you find that there is no such problem in the deployment during testing, this should be caused by the need for the third-party script to specify the corresponding domain name in the background. I tried it. If the effective domain name is not specified, this error will not appear

### Current vs. Expected behavior

I hope to be able to implement a third-party js synchronous blocking loading logic on the client side normally

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.5.0: Wed May  1 20:13:18 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6030
  Available memory (MB): 18432
  Available CPU cores: 11
Binaries:
  Node: 18.17.0
  npm: 9.6.7
  Yarn: 1.22.21
  pnpm: 7.1.0
Relevant Packages:
  next: 14.2.7 // Latest available version is detected (14.2.7).
  eslint-config-next: 14.2.7
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.5.4
Next.js Config:
  output: N/A
```


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

Script (next/script)

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

Vercel (Deployed)

### Additional context

_No response_
Repository: pytorch
Issue: Add decompositions for nanmedian and median
Labels: triaged,module: decompositions

### 🚀 The feature, motivation and pitch

https://github.com/pytorch/pytorch/pull/134819/files#diff-13f137071d25329adefbbd5df98327d792a1a9cd4eaea026b4f37b9f9ccb82aaR152

It should be pretty plausible to add decompositions for nanmedian and median that work well with compilation.

For example, something like this:
```
def nanmedian3(x):
    size = x.shape[0]
    sorted_vals = torch.sort(x)[0]
    k = ((size - 1) - sorted_vals.isnan().sum()) // 2
    return torch.ops.aten.index(sorted_vals, (k,))
```

cc: @isuruf 

### Alternatives

_No response_

### Additional context

_No response_

cc @SherlockNoMad