sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Assign key(combination) to Windows shortcut for running an app
Labels: Needs-Triage

### Description of the new feature / enhancement

When I press the key, an application of choice is started

### Scenario when this would be used?

I have an old keyboard with additional shortcut keys, but no recent drivers.
When I press the mail-app-key, nothing happens. But MS PowerToys Keyboard Manager recognises it as a specific key.
How wonderful could it be if I could assign a shortcut to my mail application using MS PowerToys Keyboard Manager to open my app of choice

### Supporting information

_No response_
Repository: vscode
Issue: Bug blocking texts with ctrl+shift+arrow
Labels: editor-core,under-discussion

<!-- ⚠️⚠️ 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

<!-- 🪓 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 and OS Version: 
Version: 1.74.3 (user setup)
Commit: 97dec172d3256f8ca4bfb2143f3f76b503ca0534
Date: 2023-01-09T16:59:02.252Z
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Windows_NT x64 10.0.22623
Sandboxed: No 

Steps to Reproduce:

1.  Block some text with **shift+arrow**
2.  Then block with **ctrl+shift+arrow**

![2023-01-19 19-04-07 00_00_00-00_00_30](https://user-images.githubusercontent.com/34857067/213438685-99af263d-fbe4-4b2e-a926-c49d30bccdd4.gif)
Repository: godot
Issue: Input Modifiers don't properly apply
Labels: bug,needs testing,topic:input

### Godot version

4.0 Beta 13

### System information

Windows 11, Vulkan, GTX 1050 Ti 527.56

### Issue description

Modifiers don't work as expected when used on the fly (holding & releasing them or Inputs that are affected by them)

Expected:
Holding W - Returns W
Starting with Shift - Returns Shift W (and possibly W and Shift Separately)

Holding Shift - Returns Shift
Starting with W - Returns Shift W (and possibly W and Shift Separately)
Stopping Shift - Returns W

Experimental Results:
Holding W - Returns W
Starting with Shift - returns W and Shift, no Shift W

Holding Shift - Returns Shift
Starting with W - Returns W, Shift W and Shift
Stopping Shift - Returns W and Shift W

### Steps to reproduce

In MRP
Hold W, then start holding Shift, Observe Results
Hold Shift, then start Holding W, and then stop Holding Shift, Observe Results


### Minimal reproduction project

[MSRP.zip](https://github.com/godotengine/godot/files/10456576/MSRP.zip)
Repository: godot
Issue: No meshes from Godot 3 conversion to 4 beta 13
Labels: discussion,topic:import

### Godot version

v4.0.beta.arch_linux [23e10d1]

### System information

Artix Linux 6.1.1-zen1-1-zen Plasma 5.26.4 Ryzen 3 3200G

### Issue description

Non builtin meshes from Godot 3.5.1 project are broken and animations/skeletons are wrong

Godot 4 :
![image](https://user-images.githubusercontent.com/69652964/213463697-eefb8117-89f8-44f7-ac34-a663fe70ccca.png)

Godot 3 : 
![image](https://user-images.githubusercontent.com/69652964/213463804-20c0c193-5f54-4aa2-9f98-c3a5399484ee.png)


### Steps to reproduce

Make a model on Blender
Import to Godot 3.5.1 and save open anyway as scene tscn
Open Godot 4 beta 13 and import 3 project
Open scene to find no mesh in the tscn file

### Minimal reproduction project

[mrp-g4.zip](https://github.com/godotengine/godot/files/10457586/mrp-g4.zip)
Repository: ant-design
Issue: Menu horizontal Submenu closes when cursor crossing from item to popup
Labels: help wanted,Inactive,unconfirmed

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/top-navigation-antd-5-1-5-forked-snyd9s?file=/demo.tsx)

### Steps to reproduce

Open Menu dropdown and place cursor about on bottom border of the item and above the popup, or move cursor across from item to popup slowly

### What is expected?

Submenu to stay open while crossing from Item to Submenu

### What is actually happening?

Sometimes Submenu closes unexpectedly, depends on how fast and precise user moves mouse cursor

| Environment | Info |
| --- | --- |
| antd | 5.1.5 |
| React | 18 |
| System | windows |
| Browser | Firefox, Chrome |

---
Two places to fix:  
Adding "pointer-events: none" to Item's css :after rule (to its bottom line)  
And syncing Popup's Align offset with popup's css :before rule. For now, Popup Align has offset 8px, but in css the offset is -7px, which should be the same -8px.

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: stable-diffusion-webui
Issue: [Feature Request]: lease add support for adding multiple webhooks
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Just add webhook support for all creations.

### Proposed workflow

1. In Setting
2. Add Webhook

### Additional information

_No response_
Repository: vscode
Issue: "Resolve in Merge Editor" button initially missing
Labels: bug,merge-editor

Type: <b>Bug</b>

In a git repository, do a merge operation which involves conflicts not automatically resolved in at least one file.
Open a file with a merge conflict, which has not recently been opened. (This could be with a direct "Open File", or by selection from the Source Control sidebar or Explorer sidebar.)

Expected result: The new editor displays, and the "Resolve in Merge Editor" button appears in the lower right corner.

Actual result: The new editor displays, with merge conflict markers colored and with "Accept" actions, but no "Resolve in Merge Editor" button appears.

Workaround: Switch to another editor tab, and then back to the editor with merge conflicts. Now the "Resolve in Merge Editor" button is present.


VS Code version: Code 1.74.3 (97dec172d3256f8ca4bfb2143f3f76b503ca0534, 2023-01-09T16:59:02.252Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: No
Remote OS version: Linux x64 3.10.0-327.el7.x86_64

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz (4 x 2400)|
|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>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<br>webgpu: disabled_off|
|Load (avg)|undefined|
|Memory (System)|7.88GB (2.18GB free)|
|Process Argv|--crash-reporter-id 85bcd4f0-c8f0-4e46-8f42-6f8e1e2778c8|
|Screen Reader|no|
|VM|0%|

|Item|Value|
|---|---|
|Remote|SSH: HOSTNAME_REMOVED|
|OS|Linux x64 3.10.0-327.el7.x86_64|
|CPUs|Intel(R) Xeon(R) Gold 6138 CPU @ 2.00GHz (4 x 1995)|
|Memory (System)|7.64GB (6.32GB free)|
|VM|100%|
</details><details><summary>Extensions (3)</summary>

Extension|Author (truncated)|Version
---|---|---
remote-ssh|ms-|0.94.0
remote-ssh-edit|ms-|0.84.0
remote-explorer|ms-|0.0.3


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
pyindex848:30577860
nodejswelcome1:30587005
282f8724:30602487
f6dab269:30613381
a9j8j154:30646983
vscsbc:30628655

```

</details>

<!-- generated by issue reporter -->
Repository: godot
Issue: Visual artifact in node select window
Labels: bug,topic:rendering,topic:2d

### Godot version

v4.0.beta13.official [caacade56]

### System information

Windows 10

### Issue description

There is a little visual artifact when selecting a node in the "Select a node" window. The artifact appears when a node is selected, not when the window opens.

![image](https://user-images.githubusercontent.com/29995442/213481024-1e949c04-4f10-4d23-ad35-fadda1466303.png)


### Steps to reproduce

1) Create a scene with a node
2) Attach a script and export a type var of the node you want to select
3) In the inspector click "Assign..."
4) The selection window opens, now select a node

### Minimal reproduction project

n/a
Repository: next.js
Issue: Rewrites don't pass response.body down when using Content-Type text/event-stream
Labels: bug

### Verify canary release

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

### Provide environment information

yarn run v1.22.19
$ /opt/app/node_modules/.bin/next info

    Operating System:
      Platform: linux
      Arch: arm64
      Version: #1 SMP PREEMPT Tue Sep 13 07:51:32 UTC 2022
    Binaries:
      Node: 18.12.1
      npm: 8.19.2
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 12.3.1
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0

warn  - Latest canary version not detected, detected: "12.3.1", newest: "13.1.3-canary.5".
        Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
        Read more - https://nextjs.org/docs/messages/opening-an-issue
Done in 2.70s.

### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue

https://not-possible.com

### To Reproduce

1. Get endpoint that responds with Content-Type: "text/event-stream" and writes to the body over time
2. next.config.js.rewrites to the endpoint
3. in `useEffect` on any page
```
const xhr = new XMLHttpRequest()
xhr.open("GET", `/rewritten`)
const interval = setInterval(() => {
  console.log(xhr.responseText)
})
```

### Describe the Bug

`xhr.responseText` is missing

### Expected Behavior

`xhr.responseText` is present

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

n/a

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

n/a
Repository: react
Issue: [DevTools Bug]: Cannot read properties of undefined (reading 'displayName') at getWrappedDisplayName
Labels: Type: Bug,Status: Unconfirmed,Component: Developer Tools

### Website or app

https://pda.ritis.org/suite/download/

### Repro steps

I noticed this when using React DevTools in my DEV environment with both Chrome and Firefox which is https://pda-dev.ritis.org/suite/download/ but I also see it in the production URL.
1.  Logged in URL with React Developer Tools 4.27.1 installed and enabled (in Chrome or Firefox)
2.  Navigate to a the Download tool
3. Almost immediate the below error displays
`
TypeError: Cannot read properties of undefined (reading 'displayName')
    at getWrappedDisplayName (react_devtools_backend.js:247:33)
    at getDisplayNameForFiber (react_devtools_backend.js:6384:62)
`
![outerType_undefined](https://user-images.githubusercontent.com/3752154/213483566-c6f2c74f-8e79-4d36-bb8a-2d55a103782c.png)
![getWrappedDisplayName](https://user-images.githubusercontent.com/3752154/213483568-af17e1d2-f713-45f3-9c82-f66369bf77f6.png)
![forwardRef](https://user-images.githubusercontent.com/3752154/213483572-1418cbc1-b0ca-4934-bbe9-cddd09ce2091.png)

I'm unable to downgrade React DevTools in Chrome, but can in Firefox and notice that this started occuring with Version 4.27.0.
- "4.27.1 Relased December 6, 2022" produces this error
- "4.27.0 Released November 28, 2022" produces this error
- "4.25.0 Released July 14, 2022" does not produce this error

Since I only use the browser version of react dev-tools, is there any way to install 4.25.0 in Chrome browser?

Other environment information:
Chrome "Version 109.0.5414.75 (Official Build) (64-bit)"
Firefox  "Version 109.0 (64-bit)
Windows 10 Pro build 19044.2486

### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

_No response_

### Error component stack (automated)

_No response_

### GitHub query string (automated)

_No response_
Repository: next.js
Issue: BigInt not supported by NextApiResponse.json()
Labels: bug,stale

### Verify canary release

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

### Provide environment information


    Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 19.3.0
      npm: N/A
      Yarn: N/A
      pnpm: 7.11.0
    Relevant packages:
      next: 13.1.2
      eslint-config-next: 13.1.2
      react: 18.2.0
      react-dom: 18.2.0

warn  - Latest canary version not detected, detected: "13.1.2", newest: "13.1.3-canary.5". 
        Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
        Read more - https://nextjs.org/docs/messages/opening-an-issue

*I checked with canary too, see the stackblitz reproduction example. This ``next info`` is from my prod environment*

### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue

https://stackblitz.com/edit/vercel-next-js-x7m1gt?file=pages/api/crash.ts

### To Reproduce

Create an API route, which tries to send a ``res.json(obj)`` where ``obj`` must contain an BigInt.

```ts
export default async function handler(
  req: NextApiRequest,
  res: NextApiResponse
) {
  const posts = {
    id: 1, // normal int
    views: 1337n, // bigint
  }

  console.log(posts);
  res.status(200).json(posts); // .json()-call will crash
}
```


### Describe the Bug

When calling ``res.json(obj)`` with an object, which contains a BigInt the API route handler will crash, due to .json not knowing how to stringify a BigInt.

### Expected Behavior

When I call ``.json()`` I expect it to **implicitly** call the corresponding ``.toString()`` method of an object when it does not know how to properly stringify an object.

Instead, I'm forced to call ``toString()`` explicitly, while the default behaviour does not add any value.

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

_No response_

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

_No response_
Repository: svelte
Issue: Typescript doesn't catch using nonexistent fields on refs
Labels: types / typescript

### Describe the bug

When using refs gotten through `bind:this`, typescript doesn't alert you if you access properties that don't exist. I'm guessing it's because interface `SvelteComponentDev` has `[accessor: string]: any`.

### Reproduction

```
// ComponentA.svelte
<script lang="ts">
  export function log() {
    console.log(5)
  }
<script>

<div>hello</div>

// ComponentB.svelte
<script lang="ts">
  import ComponentA from './ComponentA';

  let componentARef: ComponentA;

  onMount(() => {
    componentARef.logWithTypo(); // should error
  })
<script>

<ComponentA bind:this={componentARef} />
```
### Logs

_No response_

### System Info

```shell
System:
    OS: Linux 5.19 Ubuntu 22.10 22.10 (Kinetic Kudu)
    CPU: (16) x64 12th Gen Intel(R) Core(TM) i7-1260P
    Memory: 5.46 GB / 15.33 GB
    Container: Yes
    Shell: 5.2.2 - /bin/bash
  Binaries:
    Node: 18.7.0 - /tmp/xfs-bd4c206b/node
    Yarn: 3.3.0 - /tmp/xfs-bd4c206b/yarn
    npm: 8.18.0 - /usr/bin/npm
  Browsers:
    Chrome: 109.0.5414.74
    Firefox: 109.0
```


### Severity

annoyance
Repository: flutter
Issue: Clean up duplicated code between FML and third_party/accessibility
Labels: engine,a: accessibility,platform-mac,platform-windows,a: desktop,P2,c: tech-debt,team-macos,triaged-macos

//third_party/accessibility started as a fork of Chromium's accessibility code, but has diverged significantly enough that it's unlikely we'll ever merge updates from upstream. Long-term, we should probably consider a more thorough revamp into a portable, shared, flutter accessibility library but for the time being, we should eliminate any low-hanging fruit in terms of duplication.

Candidates:
* String conversion
* Logging
Repository: storybook
Issue: [Bug]: storybook web component controls args synced with URL state,
Labels: bug,has workaround

### Describe the bug

Conversation here: https://discord.com/channels/486522875931656193/1055933413565149266

When trying to open different component's storybook in the iframe then not all the args get passed to the URL. In my example I was trying to switch the icon-position from right to left and it always appears right. Also, when passing in different `href` as one of the controls then it immediately deletes when any special character gets used. 




### To Reproduce

I tried publishing this to chromatic, but having some issues: https://github.com/ariellalgilmore/storybook-issue (but it's the same setup as the lit-vite example)

I have this PR open on our current repo: https://github.com/carbon-design-system/carbon-for-ibm-dotcom/pull/9842 with a deploy preview here: https://ibmdotcom-webcomponents.s3.us-east.cloud-object-storage.appdomain.cloud/deploy-previews/9842/index.html?path=/story/components-link-with-icon--default

When you try changing `icon-placement` from right to left and then opening in an iframe you can see it still shows up on the right: https://ibmdotcom-webcomponents.s3.us-east.cloud-object-storage.appdomain.cloud/deploy-previews/9842/iframe.html?args=icon-placement:left&id=components-link-with-icon--default&viewMode=story

And if you try setting the `href` string to anything with special characters like a URL then you will see the URL remove the href string from the url


### System

```shell
Environment Info:

  System:
    OS: macOS 12.6
    CPU: (8) x64 Intel(R) Core(TM) i7-8569U CPU @ 2.80GHz
  Binaries:
    Node: 14.18.1 - ~/.nvm/versions/node/v14.18.1/bin/node
    Yarn: 1.22.17 - ~/.nvm/versions/node/v14.18.1/bin/yarn
    npm: 6.14.15 - ~/.nvm/versions/node/v14.18.1/bin/npm
  Browsers:
    Chrome: 109.0.5414.87
    Firefox: 105.0.3
    Safari: 16.0
  npmPackages:
    @storybook/addon-actions: ^6.5.13 => 6.5.15 
    @storybook/addon-docs: ^6.5.13 => 6.5.15 
    @storybook/addon-essentials: ^6.5.13 => 6.5.15 
    @storybook/addon-links: ^6.5.13 => 6.5.15 
    @storybook/addon-storysource: ^6.5.13 => 6.5.15 
    @storybook/react: ^6.5.13 => 6.5.15 
    @storybook/source-loader: ^6.5.13 => 6.5.15 
    @storybook/web-components: ^6.5.13 => 6.5.15
```


### Additional context

_No response_
Repository: vscode
Issue: Code lens is not accessible via screen reader
Labels: accessibility,under-discussion,code-lens

<!-- ⚠️⚠️ 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

<!-- 🪓 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.75.0-insider (Universal) Commit: 5ae522f8563fe48b89470923f77a9732f
- OS Version: macOS Monterey 12.6.2

Steps to Reproduce:

1. Make sure `typescript.referencesCodeLens.enabled` is set to true
2. Enable VoiceOver (System Preferences > Accessibility > VoiceOver)
3. Open a TypeScript file with code lenses, navigate to them
4. Note that they aren't highlighted by the screen reader, nor spoken out loud - I can click on the code lens using my mouse, which will open a side list with the references, and this list will be picked up by the screen reader.
Repository: TypeScript
Issue: Order of ReadonlySet/ReadonlyMap in union causes differing key inference
Labels: Bug,Has Repro,Union Order Dependence

# Bug Report

### 🔎 Search Terms

ReadonlyMap ReadonlySet key inference

### 🕗 Version & Regression Information

- This is the behavior in every version I tried.

### ⏯ Playground Link

[Playground Link](https://www.typescriptlang.org/play?ts=4.9.4#code/CYUwxgNghgTiAEYD2A7AzgF3gWygBwC54BZfAHkxgEsUBzAGnhQFdsAjEGAPgG4AoAaEiwEAM2YowGKqniikMAKJQwACwDSIAJ5l1jACpcAFLkLwASiCjBUELQGUQGXV3gAfC1Zso7pPLsYoFC0uRjAoCAg2FQBrIiMY7SJ1AEp4AF5XfXd4CVBRGhBgFKJsjzyQApQi-j55JRUNbSM+eDb4AHoO+AA9AH5W9tN6QbaE7TTM+ABvUc7u-rmAXz4UgXrlNU0dShoGeAA3JCpgYzmu3oH2nHwR6-GtSddZ64vF65W1wXBoODkJKQyFByBSbJpaABMAXghhM+CIlmsti0fmhQRCOUR3jsjmc6lCiAiUVi8USWmSTxhOQqVSKJSp5RQ+UKwFqdVBjW2EJarwWVyGtzmD0pL3ab35bU+6w5W20UN2dEYRxOZ15lzmwyFZJF5z5y1WfCAA)

### 💻 Code

```ts repro
declare const map: Map<string, number>;


declare function forEachKey<K, T>(map: ReadonlySet<K> | ReadonlyMap<K, any>, callback: (key: K) => T | undefined): T | undefined;

forEachKey(map, (key) => {}) // Error passing "map", key type is wrong (number??)

forEachKey<string, void>(map, (key) => {}) // OK; no error, key type is string


// Now, flip the union order in the parameter's type.
declare function forEachKey2<K, T>(map: ReadonlyMap<K, any> | ReadonlySet<K>, callback: (key: K) => T | undefined): T | undefined;

forEachKey2(map, (key) => {}) // Okay?

forEachKey2<string, void>(map, (key) => {}) // Still okay.
```

### 🙁 Actual behavior

<!-- What happened, and why it was wrong -->

The order of the union appears to matter, breaking inference and erroring on valid code. Swapping the union order allows the code to compile.

### 🙂 Expected behavior

<!-- What you expected to happen instead, and why -->

All of this should compile; the union ordering should not matter.