sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: [Bug]: Narrator is not announcing the label name of the checkbox in “16 passes” pane. 
Labels: bug,good first issue,help wanted,ui,accessibility,addon: a11y,sev:S3

### Describe the bug

Narrator is not announcing the label name of the checkbox in “16 passes” pane. 

Actual Result:
Narrator is not announcing the label name of the checkbox in “16 passes” pane.

Expected Result:
Narrator should announce the label of the checkbox in “16 passes” pane.

### To Reproduce

1. Open URL: [Common Navigation - Scrolling Panel ⋅ Storybook (windows.net)](https://vivacommonstorybooktest.blob.core.windows.net/$web/index.html?path=/story/common-navigation--scrolling-panel&globals=backgrounds.grid:!false;backgrounds.value:transparent)
2.  Navigate to “App bar” button at right side of the pane invoke it and navigate to “Default” link invoke it. 
3. Now navigate to “Accessibility” tab item invoke it and navigate to “16 passes” button invoke it and navigate check boxes and observe the narrator announcement. 

Attachments:

https://github.com/storybookjs/storybook/assets/93735775/bf9cc9d8-f243-43f4-acd5-0d9089f830a6

                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          

### System

```bash
OS: Windows 11
OS version: 22H2 (OS Build 22621.2134)
Edge Version: 116.0.1938.69 (Official build) (64-bit)
```


### Additional context

_No response_
Repository: storybook
Issue: [Bug]: Narrator is not announcing collapsed state for “Elements must only use allowed ARIA attributes drop down” in “Accessibility” pane.
Labels: bug,good first issue,help wanted,ui,accessibility,addon: a11y,sev:S4

### Describe the bug

Narrator is not announcing collapsed state for “Elements must only use allowed ARIA attributes drop down” in “Accessibility” pane.

Actual Result:
While navigating to the “Elements must only use allowed ARIA attributes” drop down in Accessibility pane narrator is not announcing the collapsed state of the drop down.

Expected Result:
While invoking the “Elements must only use allowed ARIA attributes drop down” in Accessibility pane narrator should announce the collapsed state of the drop down.

### To Reproduce

1. Open URL: [Common Navigation - Scrolling Panel ⋅ Storybook (windows.net)](https://vivacommonstorybooktest.blob.core.windows.net/$web/index.html?path=/story/common-navigation--scrolling-panel&globals=backgrounds.grid:!false;backgrounds.value:transparent)
2. Navigate to “App bar” button at right side of the pane invoke it and navigate to “Default” link invoke it. 
3. Now navigate to “Accessibility” tab item invoke it and navigate to “Elements must only use allowed ARIA attributes drop down” and observe the narrator announcement.


Attachments:
[collapsed state .webm](https://github.com/storybookjs/storybook/assets/93735775/ec192fab-8781-407a-a703-6c6e5e2a9c05)


### System

```bash
OS: Windows 11
OS version: 22H2 (OS Build 22621.2134)
Edge Version: 116.0.1938.69 (Official build) (64-bit)
```


### Additional context

_No response_
Repository: storybook
Issue: [Bug]: While navigating to “Brand” edit field narrator is not announcing the label name of the edit field.
Labels: bug,good first issue,help wanted,ui,accessibility,addon: controls,sev:S4

### Describe the bug

While navigating to “Brand” edit field narrator is not announcing the label name of the edit field.

Actual Result:
While navigating to “Brand” edit field narrator is not announcing the label name of the edit field.

Expected Result:
While navigating to “Brand” edit field narrator should announce the label name for “Brand” edit field.


### To Reproduce

1. Open URL: [Common Navigation - Scrolling Panel ⋅ Storybook (windows.net)](https://vivacommonstorybooktest.blob.core.windows.net/$web/index.html?path=/story/common-navigation--scrolling-panel&globals=backgrounds.grid:!false;backgrounds.value:transparent)
2. Navigate to “App bar” button at right side of the pane invoke it and navigate to “Default” link invoke it. 
3. Now navigate to “Controls” tab item invoke it and navigate to “Brand” edit field and observe the narrator announcement.                                  


Attachments:
[label name for edit field.webm](https://github.com/storybookjs/storybook/assets/93735775/0b585ca2-a604-4bf9-a636-b8bf4734a8dd)
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

### System

```bash
OS: Windows 11
OS version: 22H2 (OS Build 22621.2134)
Edge Version: 116.0.1938.69 (Official build) (64-bit)
```


### Additional context

_No response_
Repository: vscode
Issue: Language specific settings are not language specific anymore when applied to all profiles
Labels: bug,user-profiles

Type: <b>Bug</b>

VSCode supports settings, which apply to all profiles. It also has language-specific settings.

Unfortunately, both don't work well together. Consider the following user settings :

```json
"[python]": {
  "editor.formatOnSave": true
},
"workbench.settings.applyToAllProfiles": [
  "editor.formatOnSave"
]
```

The default *Format on save* settings for **all** languages are now set across all profiles. There is no way to set *Format on save* across all profiles **just for Python**.

VS Code version: Code 1.82.0 (8b617bd08fd9e3fc94d14adb8d358b56e3f72314, 2023-09-06T22:07:07.438Z)
OS version: Windows_NT x64 10.0.22621
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 7 5700G with Radeon Graphics          (16 x 3800)|
|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>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)|15.30GB (5.11GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (16)</summary>

Extension|Author (truncated)|Version
---|---|---
TabOut|alb|0.2.2
gitlens|eam|14.3.0
gitlab-workflow|Git|3.76.1
todo-tree|Gru|0.0.226
hexeditor|ms-|1.9.12
live-server|ms-|0.4.9
powershell|ms-|2023.6.0
vsliveshare|ms-|1.0.5883
git-log--graph|phi|0.1.12
vscode-yaml|red|1.14.0
vscode-coverage-gutters|rya|2.11.0
code-spell-checker|str|3.0.0
code-spell-checker-german|str|2.2.1
errorlens|use|3.13.0
intellicode-api-usage-examples|Vis|0.2.8
vscodeintellicode|Vis|1.2.30


</details>
<!-- generated by issue reporter -->
Repository: flutter
Issue: Support multi-display on Android
Labels: c: new feature,platform-android,c: proposal,P2,a: multi window,team-android,triaged-android

### Use case

Similar to https://github.com/flutter/flutter/issues/30701 and https://github.com/flutter/flutter/issues/48838

Android has also multi window/display support I would like to use this feature. This could be helpful for picture in pucture mode too.

For testing can be a second screen enabled in the developer settings of Android.

Documentation about multi display on Android can be found [here](https://developer.android.com/guide/topics/large-screens/multi-window-support#multi-display).

>![Multiple instances of an activity on multiple displays.](https://developer.android.com/static/images/guide/topics/ui/foldables/fold-multi-display.png)
>
>Figure 3. Multiple instances of an activity on multiple displays.
Repository: storybook
Issue: [Bug]:  Keyboard focus is not visible While invoking the “Tests completed” button. 
Labels: bug,good first issue,help wanted,ui,accessibility,addon: a11y,sev:S4

### Describe the bug

Keyboard focus is not visible While invoking the “Tests completed” button. 


Actual Result:
Keyboard focus is not visible While invoking the “Tests completed” button. 

Expected Result:
Keyboard focus should be visible While invoking the Tests completed” button.

### To Reproduce

1. Open URL: [Common Navigation - Scrolling Panel ⋅ Storybook (windows.net)](https://vivacommonstorybooktest.blob.core.windows.net/$web/index.html?path=/story/common-navigation--scrolling-panel&globals=backgrounds.grid:!false;backgrounds.value:transparent)	
2. Navigate to “App bar” button at right side of the pane invoke it and navigate to “Default” link invoke it. 
3. Now navigate to "Accessibility" tab item invoke it and navigate "Tests completed" button invoke it observe the keyboard focus 


Attachments:
[keyboard focus not visible tests completed.webm](https://github.com/storybookjs/storybook/assets/93735775/1a5e2859-4af3-4c75-a471-b287a2689b1b)


### System

```bash
OS: Windows 11
OS version: 22H2 (OS Build 22621.2134)
Edge Version: 116.0.1938.69 (Official build) (64-bit)
```


### Additional context

_No response_
Repository: storybook
Issue: [Bug]: Angular / Compodoc - update doc when component change
Labels: bug,has workaround,angular,argtypes

### Describe the bug

The changes made on component's properties doesn't trigger the compodoc refresh. When I add an input after starting the app, i have to restart the whole process to make it appear in the UI.

### To Reproduce

https://github.com/PillowPillow/storybook-watch-issue-repro

### System

```bash
Environment Info:

  System:
    OS: macOS 13.5.2
    CPU: (10) arm64 Apple M1 Max
  Binaries:
    Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v18.12.1/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm
  Browsers:
    Chrome: 116.0.5845.179
    Safari: 16.6
  npmPackages:
    @storybook/addon-essentials: ^7.0.6 => 7.0.6
    @storybook/addon-interactions: ^7.0.6 => 7.0.6
    @storybook/addon-links: ^7.0.6 => 7.0.6
    @storybook/angular: ^7.0.6 => 7.0.6
    @storybook/blocks: ^7.0.6 => 7.0.6
    @storybook/jest: ^0.1.0 => 0.1.0
    @storybook/testing-library: ^0.0.14-next.2 => 0.0.14-next.2
```


### Additional context

_No response_
Repository: godot
Issue: Clear hashmap after removing signals instead of erasing each key inside the loop
Labels: topic:core,topic:codestyle

### Godot version

fc99492d3066098e938449b10e02f8e01d07e2d1

### System information

Windows 11 

### Issue description

Not sure if this is really an issue, it is more a question like *Why are we doing thinks like we do them*:

When we are dropping all connections to the signals of one object, we iterate the `HashMap` and remove elements as long as the size is greater than zero:
https://github.com/godotengine/godot/blob/fc99492d3066098e938449b10e02f8e01d07e2d1/core/object/object.cpp#L1884

Wouldn't it be better to just iterate the `HashMap` without erasing the keys and then just clear it after it has been iterated?

### Steps to reproduce

Since there is no actual problem, there is no way to reproduce it.

### Minimal reproduction project

^
Repository: storybook
Issue: [Bug]:  The lists are not structured correctly in the ‘control tab’ page in “Common navigation with data transform(Desktop)”
Labels: bug,help wanted,ui,accessibility,addon: controls,sev:S3

### Describe the bug

The lists are not structured correctly in the ‘control tab’ page in “Common navigation with data transform(Desktop)”

Actual Result:
Observed that lists are not structured correctly in the ‘control tab’ page.  

Expected Result:
Ensure lists are structured correctly in the ‘control tab’ page.   

### To Reproduce

                       
1.Open URL: “[Overview - Docs ⋅ Storybook (windows.net)](https://vivacommonstorybooktest.blob.core.windows.net/$web/index.html?path=/docs/overview--docs)”
2. In left navigation select “Common navigation with data transform(Desktop)” and invoke it.  
3. In right page navigate to ‘control tab’ item and invoke it.  
4. Now Run the Accessibility insights for wed for the opened page.   


Attachments:


![Ellipsis menu-control tab](https://github.com/storybookjs/storybook/assets/93735775/a3b2e2d8-37fa-4806-9fae-bccdd5930612)


![Panel-control tab](https://github.com/storybookjs/storybook/assets/93735775/5f13152f-4f5b-4998-9778-a9bee5944d95)


![Navigation link-control tab](https://github.com/storybookjs/storybook/assets/93735775/79214873-e55d-4db8-be2a-179121f3b34d)


![Narrator announcement (1)](https://github.com/storybookjs/storybook/assets/93735775/4ba04c30-b1ac-425c-8876-f9e7d84d0156)


![Flyout menu-control tab](https://github.com/storybookjs/storybook/assets/93735775/e945b3fe-34e3-4bd6-8ab5-c233d4182b2a)


![Fast pass-Common navigation with data transform(Desktop)](https://github.com/storybookjs/storybook/assets/93735775/fbed72f2-971a-48ce-a023-f2bea9f2a9f7)


![Fast pass issue (1)](https://github.com/storybookjs/storybook/assets/93735775/eddfb51d-6212-4830-8a4a-0ea92a690500)


### System

```bash
OS: Windows 11
OS version: 22H2 (OS Build 22621.2134)
Edge Version: 116.0.1938.69 (Official build) (64-bit)
```


### Additional context

Observation: Narrator announces<< RAW moduleStatusResult :{ appCatalog :[...] 5 items licenseDetails :[...] 2 items }, >>.  
 
NOTE: The same issue observed in the Left navigation in “Ellipsis Menu”, “Flyout”, “Navigation Link” and “panel”.  
Navigation path: 
Ellipsis-->‘Control tab’ page – “Support menu item field “
Flyout -->‘Control tab’ page – “Content field”
Navigation link-->control tab page -->“Icon Field”
Panel-->control page – “Top field”
Repository: three.js
Issue: More flexible material override
Labels: Enhancement

### Description

I want to render my scene for reflections. For that I want to replace all materials with simpler variants. Currently the only possible override is `scene.overrideMaterial`, but sometimes the materials in scene are so different it is hard to replace them with one material only.

### Solution

I suggest extending this by adding a new member - `scene.mapMaterial`, which would be a function receiving material and returning material, allowing to map any material and replacing is as desired (often one could implement it using a simple hashmap holding alternative representations of the material).

### Alternatives

One possible alternative is to clone the whole scene and replace the materials on all objects. Another alternative is to control material detail using material defines or uniforms, but that requires updating all materials at least twice in each frame.

### Additional context

To avoid additional tests, current functionality  of `overrideMaterial === null ? renderItem.material : overrideMaterial` would be handled by a default value of `mapMaterial`, containing this code wrapped in a function.

The solution would allow functionality similar to what is currently done for shadow maps in `getDepthMaterial` function.

If the idea seems reasonable, I will be glad to prepare PR.
Repository: pytorch
Issue: The following will always fail on NixOS
Labels: module: cudnn,triaged,topic: build

https://github.com/pytorch/pytorch/blob/9a492fc27f3f1f0f71ed8b24704430a87a99cec9/torch/utils/collect_env.py#L168

```
❯ ldconfig -p | grep libcudnn | rev | cut -d" " -f1 | rev
ldconfig: Can't open cache file /nix/store/46m4xx889wlhsdj72j38fnlyyvvvvbyb-glibc-2.37-8/etc/ld.so.cache
: No such file or directory
```

I'm guessing this should be able to be overridden by supplying your own CUDNN_LIBRARY environment variable or something along those lines.

I came across this issue when trying to debug why i'm getting the following on a nix system.

```
pip install -r requirements.txt
ERROR: torch-1.12.1+cu116-cp39-cp39-linux_x86_64.whl is not a supported wheel on this platform.
```

cc @csarofeen @ptrblck @xwang233
Repository: godot
Issue: [MacOS] IDE / GUI: Cursor "press" action is ignored
Labels: bug,topic:input,topic:gui

### Godot version

4.1.1 Stable

### System information

Mac OS Godot v4.1.1.stable - macOS 13.5.2 - Vulkan (Forward+) - integrated Apple M1 - Apple M1 (8 Threads)

### Issue description

On MacOS (and maybe other OSes), there is a particular L/R mouse button behavior behavior that is hard to live without under certain circumstances, I don't know whether it has an official name but let's call it "click and hold".

So, when the user presses and holds, for example, LMB on a menu, the selection highlight appears and stays on the menu as long as the button is kept pressed. When the button is released, whatever was under the highlight / cursor is selected. Note that this behavior **saves you basically two out of four finger movements** when compared to the standard "two clicks required for simple operations: one to open the menu, and then select something" where you have to perform 4 finger actions (finger press down, lift up, press down, lift up) and this way you can do it with only 2 (finger down, finger up).

This behavior is especially comfortable (kind to wrists) to use with graphic tablet if you're an artist for example, and use a pen instead of a mouse most of the time.

In Godot 4, the "click and hold" method works on all the top menus (Godot, Scene, Project, Debug Editor, Help) but not in the IDE: if I right click on, for example, a scene in the FileSystem panel and keep the RMB pressed, the highlight / selection does not appear (only the menu opens). So I have to click on the menu again just to select an entry. Always throws me off.

### Steps to reproduce

Open Godot.

Correct behavior:
Position your mouse over any top menu, for example "Scene".
Press and hold RMB (don't let go)!
Now drag the cursor a bit down, to, say, New Scene.
Release RMB.
A new scene will be created!
So it looks like this, note there's only one RMB press in the operation:
https://github.com/godotengine/godot/assets/106015575/ec932262-24f6-450f-a895-54632522cf32



Strange behavior:
Position your mouse over a scene in the FileSystem panel.
Press and hold RMB.
The menu opens, but there is no highlight marker!
Even if you wiggle the cursor out of the just opened menu area, nothing will happen.
Now you have to release RMB for the highlight marker to appear…
…and the click again.

### Minimal reproduction project

N/A
Repository: pytorch
Issue: Cannot install torchmetrics - ERROR 403
Labels: high priority,module: binaries,triaged

### 🐛 Describe the bug

Torchmetrics wheel seems to have broken permission - https://download.pytorch.org/whl/torchmetrics-1.0.3-py3-none-any.whl 
```
docker run --rm -ti ubuntu:18.04
```
inside the docker
```
apt update && apt install python3.7 python3-pip -y && pip3 install --upgrade pip && \
python3.7 -m pip install pytorch-lightning --extra-index-url=https://download.pytorch.org/whl/cu113/
```
error
```
HTTP error 403 while getting https://download.pytorch.org/whl/torchmetrics-1.0.3-py3-none-any.whl (from https://download.pytorch.org/whl/cu113/torchmetrics/)
```

### Versions

NA

cc @ezyang @gchanan @zou3519 @kadeng @seemethere @malfet
Repository: vscode
Issue: Diff Algorithm: Improve insertion point
Labels: feature-request,diff-editor

## Description

Weird insertion point

![Image](https://github.com/microsoft/vscode/assets/2931520/ad8cc393-442c-4a22-b09a-d730b371f0c4)

## Playground Example

[Monaco Editor Playground Repro](https://microsoft.github.io/monaco-editor/playground.html?source=v0.42.0-dev-20230911#XQAAAALwDwAAAAAAAABBqQkHQ5NjdMeMm-jY7SIQ9S7DNlzs5W-mwj0fe1ZCDRFc9ws9XQE0SJE1jc2VKxhaLFIw9vEWdz-byd4G7VAV7Ji5IwtXa3dN4YhVMeJO830nEa36EWpR5RYaCSG4vUxAZHnDtzQng1vTMQbhSR9wMaseKJaekya3NLsyOdCXfXXA0uQFfhfrHn6XP65jboRN1Lw4HZxhL-NelWSvjPVT4SOFQ2AU6ibD0BxAp2g_cocN-8q_2RZgWHE-_xNeWRktSEoQZzeM947oeJ3L_0SYFsMYBP4v3OxHOiMUsMITuEcKwYxqVDhGBW3IUSUVsVS5uJh2XJmXvLaK5hvIUPzG89DLgZFbhNzQ02N4svHUjgRuAjKydc-xxjzdjUi3ogVWD8vVfNI6Cvn-kS2AKcunUfcLPhAc9ZUtj-h3ZKV1L8iIozpW1MUCweqGA7NStlIUHiz6a-CgT21lC83tEzKTJGTYY_5Co-DRU2dWNfFkbUlQHCbTCYCzpUbhFoYZ1Zzh76qjdr0UCtVp2K0wfpeQNZvJOFbSSPw7JRbLxQZRlTUNKTDP91YHtnD1LxEYGEbjnXvOIr_hfpSJjSLq-4GIEkWrMOttOLV3dZhQfXa-2mpATu5c2m8nqbdhKTbSXYVoHq6sBOrnSweFoguJXFMH2O6Pq4GHEumvO6Hpq9xjMzNC8rjCWA4r9D6B0sIPXvDOKg84RBDCgU0AErCugQBlOeqwGEtvwJnd1nvjEo62a9pcw6nfMzOw8tD5zC6Tw5apn4H6WI6lJD6qGVWFy8CjPcyhYyYanYjAPA0EAScQMBdwaHI1qnawCnvSKLyUWPXHmKN6jb0AuE7oOs4mFuGcxCkPISu7S0VpK_tl4EZUQk_Qlw0jHjl6gX2jNEJ-Wl-vYtFo9UKi5zQPPlTb1rKjyu6VaW8Xa4mNgo2UDcUCpMKKX8QbLWSF7vU9KRP0pX4W_vhtt_Glca5YZ_d5XMLpTm-03vDNaEnHvPYWA62I7dQ1Rfzzl1K3NQ73u1h5WsSunRDBTwIUaIfjwdDSEppsAo1ywZ01MS6N02-nApsGdvh8yGUxfApb2OumDQGFq_ugX1CBI4Edc5DjlU_-rvgt-R6km8rQVO_owHjQi2X1lr1ZMVGGHjgVFeIP7roVb_8v-lTiX3feZKWG2GshGYACCXfChMFvox7WHvYgpUz1wDNY_Cqh38-3WTHxNX-UsXBIu8T-c69cZY66BVetoUHmjm2xFJKqAM2LQDIuhTN7n7dLvCzTz_eHcI9uKcDAqSfTMrNqw6i4izfa09T81BHordC_ANvg4g87sXgewoD-Zli-L91prnsKHB_2yiVaMlWj-1M7eqKqpkAmz2hlAF1BfFaoJlUbH9_SQRIan-jYnLMh96xVWE5LRDwYc4BpUImzG-vndzqw59gUvdrlUickBHDMY9I0oTpimQrV60E4tqNx8DpyAxuYlx-GiQSymrOLyFB6CrL0-zLALGbVk_CifHcQP97qMuk3HpwZUydR69BH46zlAnGTMk0rbhxIo2P5Z3GTlAi8ILB7Dv8SzYB4b8CYBdk91szNi9hPzQLXA7SZgOge9taz-y09DnKCke9aNfaiemfcSPqw_veucpVlHEWPVU4pR94VKYACkHualBdWvyxTOSt_nQ6faHKkvTO9TS6GxirCqRmQjyd2wTLJOdIeox7jU2PBcJQB77itLFC0balNj94nDoy341qNRBbXqUAGtNEqLqM3JGpmCP-J_3s6) (click on "compare with latest dev" to verify a future bug-fix)