sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: [Power Toys - Fancy Zones]: Focus gets lost when user activates the 'Create a New layout' button.
Labels: Issue-Bug,Area-Accessibility,Needs-Triage,A11yE+D,A11ySev3,A11yWCAG

### Microsoft PowerToys version

0.55.2

### Running as admin

- [ ] Yes

### Area(s) with issue?

FancyZones Editor

### Steps to reproduce

**Test Environment:**
OS: Windows 11 Version Dev (22538.1010)
App version: 0.55.2
App name: Power Toys
Screen Reader: Narrator

**Repro Steps:**

1. Navigate on desktop tool bar using keyboard and navigate to Show hidden icons combo box and activate it.
2. Now navigate to Power toys Fancy Zones on navigation pane and activate it.
3. Press the shortcut to activate fancy zones editor.
4. Navigate to Create a New Layout button and activate it.
5. Observe if focus gets lost or not.

**User Impact:**
If focus order is not aligned with either the meaning or operation of the UI, it would be confusing for the Keyboard dependent users who navigate documents sequentially and expect the focus order to be consistent with the sequential reading order 

**Guideline Reference:**
https://www.w3.org/WAI/WCAG21/Understanding/focus-order.html

https://user-images.githubusercontent.com/87321414/155475458-32f1ca92-7fb7-4e50-bd4c-1b920e439539.mp4




### ✔️ Expected Behavior

Focus should navigate to the first interactive element as soon as the dialog opens. Also, screen reader should announce information about the dialog.

### ❌ Actual Behavior

Focus gets lost when user activates the 'Create a New layout' button. User has to press tab key to navigate to the first interactive element. Also, screen reader does not announce any information about the dialog.

### Other Software

_No response_
Repository: flutter
Issue: There should be no default page transitions for desktop and web platforms.
Labels: c: new feature,framework,a: animation,f: material design,f: routes,customer: google,c: proposal,a: desktop,P3,team-design,triaged-design

As page transitions are not common on desktop and web applications, the default transitions on these platforms should be removed.

An attempt at this was tried with #82596, but it had an issue with the [delay was still occurring](https://github.com/flutter/flutter/issues/88221) even though the transition gone.
Repository: transformers
Issue: Add OFA to transformers
Labels: New model

# 🌟 New model addition
We recently proposed OFA, a unified model for multimodal pretraining, which achieves multiple SoTAs on downstream tasks, including image captioning, text-to-image generation, referring expression comprehension, etc. We would like to implement OFA on transformers if it is possible.

## Model description
OFA is a unified multimodal pretrained model that unifies modalities (i.e., cross-modality, vision, language) and tasks (e.g., image generation, visual grounding, image captioning, image classification, text generation, etc.) to a simple sequence-to-sequence learning framework. For more information, please refer to our paper: [Unifying Architectures, Tasks, and Modalities Through a Simple Sequence-to-Sequence Learning Framework](http://arxiv.org/abs/2202.03052).

<!-- Important information -->
Our code base is Fairseq. We wonder if there is any simpler solution for the transfer from Fairseq to transformers. To email us, please contact zheluo.wp@alibaba-inc.com or junyang.ljy@alibaba-inc.com.

## Open source status

* [x] the model implementation is available: ([OFA official repo](https://github.com/OFA-Sys/OFA))
* [x] the model weights are available: ([OFA checkpoints](https://github.com/OFA-Sys/OFA/blob/main/checkpoints.md))
* [x] who are the authors: (Peng Wang @[logicwong](https://github.com/logicwong), An Yang @[yangapku](https://github.com/yangapku), Rui Men @[jxst539246](https://github.com/jxst539246), Junyang Lin @[JustinLin610](https://github.com/JustinLin610), Shuai Bai, Zhikang Li, Jianxin Ma, Chang Zhou, Jingren Zhou, Hongxia Yangf)
Repository: PowerToys
Issue: [Power Toys - Fancy Zones]: Position is not announced for Grid/ Canvas radio buttons on Create a new layout dialog.
Labels: Issue-Bug,Area-Accessibility,Needs-Triage,A11yE+D,A11ySev3,A11yWCAG

### Microsoft PowerToys version

0.55.2

### Running as admin

- [ ] Yes

### Area(s) with issue?

FancyZones Editor

### Steps to reproduce

**Test Environment:**
OS: Windows 11 Version Dev (22538.1010)
App version: 0.55.2
App name: Power Toys
Screen Reader: Narrator

**Repro Steps:**

1. Navigate on desktop tool bar using keyboard and navigate to Show hidden icons combo box and activate it.
2. Now navigate to Power toys Fancy Zones on navigation pane and activate it.
3. Press the shortcut to activate fancy zones editor.
4. Navigate to Create a New Layout button and activate it.
5. Turn on narrator.
6. Navigate to Grid/ Canvas radio buttons.

**User Impact:**
If the correct information and relationships are not provided, it would be difficult for people with different disabilities as the information and relationships that are implied by visual or auditory formatting will not be preserved when the presentation format changes. Having these structures and these relationships programmatically determined or available in text ensures that information important for comprehension will be perceivable to all.  

**Guideline Reference:**
https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships.html

https://user-images.githubusercontent.com/87321414/155481066-48a492a8-5dd7-4d68-a4d0-79e5435d39c4.mp4




### ✔️ Expected Behavior

Position should be announced for Grid/ Canvas radio buttons on Create a new layout dialog.

### ❌ Actual Behavior

Position is not announced for Grid/ Canvas radio buttons on Create a new layout dialog

### Other Software

_No response_
Repository: excalidraw
Issue: Transparent stroke
Labels: enhancement

To set stroke color to transparent, we have to manually write "transparent" in the color code field.

I think we should have a button for that, just as for the background color.

Use case : as far as I'm concerned I often draw plain colored shapes with no "border".
Repository: material-ui
Issue: [Autocomplete] `getOptionLabel` callback is getting the value instead of option object
Labels: docs,component: autocomplete

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

When using different types for `options` and `value` properties, the `getOptionLabel` method is passed value instead of option object. 

let's say I'm using following types:

```TS
type Option = { label: string; value: any; group?: string }
type Value = string;
```
I'm expecting getOptionLabel method always passed an Option type but that's not the case. That's why the picked option can not be displayed properly. 

```JS
getOptionLabel={(option) => option.label || "!!!"} //here sometimes Value type is passes instead of Option type.
isOptionEqualToValue={(option, value) => return option.value === value}
```


### Expected behavior 🤔

Always pass and option to `getOptionLabel` as a param to be consistent. 

### Steps to reproduce 🕹

Here's a demo:
https://codesandbox.io/s/controllablestates-material-demo-forked-0lekyg?file=/demo.js

Steps:

1. Render a controlled Autocomplete component using different types for `options` and `value`  props. (object and string)
2. Utilize `isOptionEqualToValue` and `getOptionLabel` callback props

### Context 🔦

I'm trying to render options that are objects like {label:"Label", value:"some value"}, but I want to use the value of the selected option instead of the whole option object. 

### Your environment 🌎

_No response_
Repository: vscode
Issue: Unify download size limit dialog/notification
Labels: search,under-discussion

Testing #143575

Text search shows:
<img width="529" alt="image" src="https://user-images.githubusercontent.com/9205389/155510075-4f67fed6-5493-4dcb-9d8b-8f73fd3ba52e.png">

Reference search shows:
<img width="458" alt="image" src="https://user-images.githubusercontent.com/9205389/155511339-6f8c61bc-d1a0-4361-8824-45e8073ca73e.png">

Should reference search show the same dialog with the same options as text search?
Repository: vscode
Issue: Download limit dialog says "(null)" when the settings is 0
Labels: feature-request,search,web

Testing #143575

Setting 0 as the index limit shows a dialog mentioning "(null)" when using text search:
<img width="585" alt="image" src="https://user-images.githubusercontent.com/9205389/155512079-c7606f1b-a307-4a93-b229-daa5fa44e7b4.png">

The setting might be easier to understand if there was an additional setting with the values 'never download', 'ask before downloading' and 'download with limit'. Currently these 3 options are squeezed into the max index size setting.
Repository: flutter
Issue: [Proposal] Add directionality to CupertinoActionDialog
Labels: c: new feature,framework,a: internationalization,f: cupertino,c: proposal,team-design,triaged-design

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case

<!--
     Please tell us the problem you are running into that led to you wanting
     a new feature.

     Is your feature request related to a problem? Please give a clear and
     concise description of what the problem is.

     Describe the alternative solutions you've considered. Is there a package
     on pub.dev/flutter that already solves this?
-->

Flutter version 2.8.1 
I observed that Material version of AlertDialog uses OverflowBar which takes care of directionality automatically, it moves along x axis and adds value to it when direction is ltr and removes value when direction is rtl, so actions are automatically flipped there. It is not the case with CupertinoAlertDialog, actions are not flipped when switching between rtl/ltr languages, checks have to be done manually.

## Proposal

<!--
     Briefly but precisely describe what you would like Flutter to be able to do.

     Consider attaching something showing what you are imagining:
      * images
      * videos
      * code samples

     Does this have to be provided by Flutter directly, or can it be provided
     by a package on pub.dev/flutter? If so, maybe consider implementing and
     publishing such a package rather than filing a bug.
-->

It would be nice to align CupertinoAlertDialog with AlertDialog if possible so it can flip actions automatically by default. It may cause potential minor bugs when someone aims to create platform dependant dialogs and forgets to do proper directionality checks of actions from Cupertino side.
Repository: terminal
Issue: We shouldn't have our own startup setting, we should just use the OS one
Labels: Help Wanted,Issue-Bug,Area-UserInterface,Product-Terminal,Priority-2

From MSFT:34529127



> Steps to repro:
> 1. Open Settings - App - Start up.
> 2. Enable start up setting for Windows Terminal.
> 3. Reboot.
>
> Expected results:
> Windows Terminal can launch automatically after enter desktop and App start up setting should be on for Windows Terminal.
> Actual results:
> Windows Terminal can launch automatically after enter desktop, but App start up setting become off for Windows Terminal.

----

More notes, circa Dec 2023:

Okay so we all re-read all the docs and I think we were wrong entirely here. 

We should have never had this setting in our settings JSON in the first place. It should have always just been backed by the OS setting. This probably dates back to us just having a JSON settings file. We should make the settings in the Terminal Settings UI reflect the OS settings. We shouldn't maintain our own _separate_ setting. 

> We need the Windows Settings Startup being Enabled to trigger Windows to start Terminal on next reboot.
And, we need the Terminal Settings Startup to be Enabled, to keep it in the Enabled state for Windows. If this is not enabled, when Windows launches Terminal after reboot, Terminal app itself disables the startup task here: https://github.com/microsoft/terminal/blob/306f31acf482ce84701aabee52981575277f16bb/src/cascadia/TerminalApp/AppLogic.cpp#L382
> 
> Quickly glancing through the Terminal code, Terminal Settings Startup relies on "`startOnUserLogin`" value and is saved in a default file. This value does not change if the user changes startup state in Windows Settings. 
>  
> I am not sure, why the startup task is disabled when `StartupTaskState::Enabled` in the above link. But in my opinion it shouldn't be disabled if the user has enabled it in Windows settings. and use the value returned by `StartupTask::GetAsync(StartupTaskName)` for "`startOnUserLogin`".

> [!Note]
> ## Walkthrough

I need to write a new one!

We need to:
* Ditch the old setting entirely. 
* Make the toggle in the Settings tab reflect the OS setting
* probably remove `Enabled="false"` from our manidest, ala #16244
Repository: vscode
Issue: Explorer should expand folder that is added
Labels: bug,file-explorer,workbench-multiroot,web,vscode.dev

Extracted from https://github.com/microsoft/vscode/issues/143857

I noticed that calling `IWorkspaceEditingService#updateFolders` shows the new folders collapsed and not expanded. Would be great if we could change that to improve the experience opening a folder on vscode.dev:

![Recording 2022-02-24 at 12 34 59](https://user-images.githubusercontent.com/900690/155516724-e2392bf1-5cc2-4ee0-987b-ec2e0ac0f6d2.gif)


//cc @isidorn
Repository: terminal
Issue: Double Close Popup
Labels: Help Wanted,Issue-Bug,Product-Terminal,Priority-3,Area-Windowing

From MSFT:37868165

> Hovering over the close window button in Windows Terminal for a certain period of time will show two hover popups both showing "Close".

Looks like we get the xaml popup and the user32 one. Easiest fix would be to get rid of the xaml one, but then it would be different from the others. 

We may want to explore not having a user32 titlebar at all in tabs in titlebar mode.
Repository: vscode
Issue: Markdown hover - table border is not being shown in the hover
Labels: markdown,polish,editor-hover

Testing #143574

Notice how the table at the bottom of the hover does not have borders.

![image](https://user-images.githubusercontent.com/3372902/155525863-13fbf422-bcf5-416f-a68a-2a573341a8f5.png)
Repository: rust
Issue: generic_const_expr: doc test does not compile while similar lib test compiles fine
Labels: A-diagnostics,T-compiler,D-terse,F-generic_const_exprs

**Update(fmease, 2024-01-24)**: https://github.com/rust-lang/rust/issues/94321#issuecomment-1052583523:

> This issue goes away if the doc tests have the `#![feature(generic_const_exprs)]` flag enabled.

I realized thanks to https://github.com/rust-lang/rust/issues/94287#issuecomment-1051679147; maybe a better diagnostic could help here.

---
---

The doc test for `foo` and the test `tests::test` contain the same code (the only difference is the `use` statement which has to be different). The lib test passes but the doc test fails to compile.

```rust
#![feature(generic_const_exprs)]

pub struct If<const CONDITION: bool>;
pub trait True {}
impl True for If<true> {}

pub struct FixedU64<const FRAC: u32>;

/// ```rust
/// use fcg5::{foo, FixedU64};
/// foo(FixedU64::<4>);
/// ```
pub fn foo<const FRAC: u32>(_fixed: FixedU64<FRAC>)
where
    If<{ FRAC <= 64 }>: True,
{
}

#[cfg(test)]
mod tests {
    #[test]
    fn test() {
        use crate::{foo, FixedU64};
        foo(FixedU64::<4>);
    }
}
```

`cargo +nightly test`:
```
   Compiling fcg5 v0.1.0 (/home/trevor/try/fcg5)
...
    Finished test [unoptimized + debuginfo] target(s) in 0.44s
     Running unittests src/lib.rs (target/debug/deps/fcg5-877f755fe1bd39e7)

running 1 test
test tests::test ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

   Doc-tests fcg5
...

running 1 test
test src/lib.rs - foo (line 9) ... FAILED

failures:

---- src/lib.rs - foo (line 9) stdout ----
error[E0277]: the trait bound `If<{_: bool}>: True` is not satisfied
  --> src/lib.rs:11:1
   |
5  | foo(FixedU64::<4>);
   | ^^^ the trait `True` is not implemented for `If<{_: bool}>`
   |
   = help: the following implementations were found:
             <If<true> as True>
note: required by a bound in `foo`
  --> /home/trevor/try/fcg5/src/lib.rs:15:25
   |
15 |     If<{ FRAC <= 64 }>: True,
   |                         ^^^^ required by this bound in `foo`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0277`.
Couldn't compile the test.

failures:
    src/lib.rs - foo (line 9)

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.02s

error: test failed, to rerun pass '--doc'
```

### Meta

`rustc +nightly --version --verbose`:
```
rustc 1.61.0-nightly (532d3cda9 2022-02-23)
binary: rustc
commit-hash: 532d3cda90b8a729cd982548649d32803d265052
commit-date: 2022-02-23
host: x86_64-unknown-linux-gnu
release: 1.61.0-nightly
LLVM version: 14.0.0
```
Repository: godot
Issue: Viewport "Render Direct To Scene" crashes the editor
Labels: bug,topic:rendering,confirmed,crash

### Godot version

v3.4.2.stable.official.45eaa2daf

### System information

Arch Linux (x86_64 latest), GLES2

### Issue description

Given a project on GLES2, a Viewport node with Fxaa enabled, a Spatial node and a Camera as a child of the Viewport node: enabling the Viewport node's render_direct_to_screen property will crash the editor.

This occurs on multiple computers with different GPUs, so I don't think the GPU model and driver version are relevant.

```
Godot Engine v3.4.2.stable.official.45eaa2daf - https://godotengine.org
OpenGL ES 2.0 Renderer: AMD Radeon RX 580 Series (POLARIS10, DRM 3.42.0, 5.15.24-2-lts, LLVM 13.0.1)
OpenGL ES Batching: ON
 
ERROR: FATAL: Index p_index = 0 is out of bounds (size() = 0).
   at: get (./core/cowdata.h:156)

================================================================
handle_crash: Program crashed with signal 4
Engine version: Godot Engine v3.4.2.stable.official (45eaa2daf1e3d2571a9f31a3421911262ec82f51)
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
[1] /usr/lib/libc.so.6(+0x42560) [0x7f01414d5560] (??:0)
[2] ./Godot_v3.4.2-stable_x11.64() [0x13444b2] (??:0)
[3] ./Godot_v3.4.2-stable_x11.64() [0x27e0536] (??:0)
[4] ./Godot_v3.4.2-stable_x11.64() [0x2e92a75] (??:0)
[5] ./Godot_v3.4.2-stable_x11.64() [0x27d3a69] (??:0)
[6] ./Godot_v3.4.2-stable_x11.64() [0x27f25c0] (??:0)
[7] ./Godot_v3.4.2-stable_x11.64() [0x9d8ef3] (??:0)
[8] ./Godot_v3.4.2-stable_x11.64() [0x94655d] (??:0)
[9] /usr/lib/libc.so.6(+0x2d310) [0x7f01414c0310] (??:0)
[10] /usr/lib/libc.so.6(__libc_start_main+0x81) [0x7f01414c03c1] (??:0)
[11] ./Godot_v3.4.2-stable_x11.64() [0x95a18e] (??:0)
-- END OF BACKTRACE --
================================================================
Aborted (core dumped)
```

### Steps to reproduce

1. Open the minimal reproduction project.
2. Select the Viewport node.
3. Enable the "Render Direct To Screen" property in the Inspector.
4. Crash.


### Minimal reproduction project

[SampleProject.zip](https://github.com/godotengine/godot/files/8133111/SampleProject.zip)
Repository: pytorch
Issue: Review and refactor  the way libcublas static libraries are linked
Labels: module: build,oncall: releng,triaged,module: cublas

As part of working on this issue:  [here](https://github.com/pytorch/pytorch/issues/67905) 

We found that libcublas is now required for using cudnn. Following [PR](https://github.com/pytorch/builder/pull/971) adds libcublas dynamic module to torch libraries .

However it looks like we still link libcublas statically in following files:

(.venv) [~/local/pytorch] git grep libcublas
aten/src/ATen/CMakeLists.txt:      ${CUDA_TOOLKIT_ROOT_DIR}/lib64/libcublas_static.a
cmake/public/cuda.cmake:        "${CUDA_TOOLKIT_ROOT_DIR}/lib64/libcublas_static.a")
cmake/public/cuda.cmake:      "${CUDA_TOOLKIT_ROOT_DIR}/lib64/libcublasLt_static.a")
cmake/public/cuda.cmake:    # libcublasLt_static.a.o): undefined reference to symbol 'cudaStreamWaitEvent'

We want to review each use case and determine if this static linking is required and if we can use dynamic linking instead since we already including this library with our binary builds. We should refactor the code to use dynamic linking if static is not required or properly document if static linking is required and why we should keep it.


### Versions

1.11

cc @malfet @seemethere @csarofeen @ptrblck @xwang233
Repository: storybook
Issue: Accessibility checks are different for the same story
Labels: bug,help wanted,addon: a11y

**Describe the bug**
Accessibility checks are different for the same url with Chrome 98.0.4758 and Safari 15.0. 
It's work on Firefox 97.0.1

**To Reproduce**

Link to the storybook : https://61fd537ecf081f003a135235-nndgxdlrso.chromatic.com/?path=/story/button--inaccessible

Step 1 : I click on the url and I see the accessibility checks  of the first component (button-inaccessible) with 
`1 violations | 4 assists | 0 incomplete`

Step 2 : I click on another component (ex: button-accessible) and I come back to the first one (button-inaccessible). 

Step 3 :  I have different values for the first component and all the other components have the same accessibility checks values : 
`0 violations | 1 assist | 0 incomplete`

**System**
```
Environment Info:

  System:
    OS: macOS 11.6
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Binaries:
    Node: 16.13.2 - ~/.nvm/versions/node/v16.13.2/bin/node
    Yarn: 1.22.10 - ~/.nvm/versions/node/v12.22.1/bin/yarn
    npm: 8.1.2 - ~/.nvm/versions/node/v16.13.2/bin/npm
  Browsers:
    Chrome: 98.0.4758.102
    Firefox: 97.0.1
    Safari: 15.0
  npmPackages:
    @storybook/addon-a11y: ^6.4.18 => 6.4.19 
    @storybook/addon-actions: ^6.4.18 => 6.4.18 
    @storybook/addon-essentials: ^6.4.18 => 6.4.18 
    @storybook/addon-links: ^6.4.18 => 6.4.18 
    @storybook/addon-react-native-web: ^0.0.18 => 0.0.18 
    @storybook/react: ^6.4.18 => 6.4.18 
```

**Additional context**
PR : https://github.com/pass-culture/pass-culture-app-native/pull/2694
Repository: go
Issue: cmd/go: clarify documentation for `-overlay` file additions
Labels: Documentation,help wanted,NeedsFix

Currently, it's possible to replace files using `-overlay` (https://github.com/golang/go/issues/39958).

--------

However, it only have `Replace` options:

```
type OverlayJSON struct {
	Replace map[string]string
}
```

I would like to suggest a new field, may named as `Additions`:

```
type OverlayJSON struct {
        Additions map[string]string
	Replace map[string]string
}
```

-----------------

That is useful when using code-generation/meta-programming. In those cases, would be possible to create new go files, or even creating files such as assembly code (`.s`) or creating syso files (`.syso`), without need to write it into the package directory. Currently, those files must be written into the package itself, but the `-overlay` could be used instead.