sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Fancy Zones layouts by resolution or aspect ratio
Labels: FancyZones-Layouts,Needs-Triage

### Description of the new feature / enhancement

Fancy Zones do not currently allow automatically changing the layout selected on a monitor when its resolution changes to a different size. That would be particularly useful when switching a monitor from a horizontal position to a vertical position.

In the current behaviour, the layout that is set when horizontal will just be stretched to fit the vertical orientation but that results most of the time in not-very-useful or useless zones. If the same monitor with 1920x1080 (16:9) would be considered different from the same monitor with 1080x1920 (9:16), then we could set a new layout and that would then automatically be changed between the two.

### Scenario when this would be used?

The most common scenario would be when a monitor is switched from horizontal to vertical. (but it can be in any situation in which a new resolution is set)

### Supporting information

![example](https://user-images.githubusercontent.com/22453858/174036240-64939564-00d7-40a3-a32a-29ffb37e9d20.png)
Repository: flutter
Issue: Add support for full screen `DatePicker` dialog
Labels: framework,f: material design,P2,team-design,triaged-design

Part of https://github.com/flutter/flutter/issues/91605

Requires https://github.com/flutter/flutter/issues/104961

Add support for full screen `DatePicker` using [Tokens](https://github.com/flutter/flutter/blob/master/dev/tools/gen_defaults/data/date_picker_docked.json)


| Date Selection | Date Input |
| --------------- | --------------- |
| <img src="https://user-images.githubusercontent.com/48603081/174062401-d7d10a48-fcc8-451b-ade1-4e727976cee4.png"  /> | <img src="https://user-images.githubusercontent.com/48603081/174062409-c0f4978e-2b82-4437-aa24-b74d833e96d9.png"  /> |
Repository: vscode
Issue: Suggestion box has the wrong height in case of a small window size
Labels: bug,ux,suggest

<!-- ⚠️⚠️ 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.67.1
- OS Version: macOS 12.3.1

Steps to Reproduce:

1. Open a code file
2. Vertically resize the VS Code window to make it about 200px high
3. Start typing a term that's valid for the language of the open file, to make suggestions appear.
4. Observe how the suggestions box has the wrong height.

Or see this [2-min video](https://www.loom.com/share/e152bce924c746d993d66ec29089f58b) where I demo the behavior.
Repository: godot
Issue: FileDialog in "Open File" mode won't update the title window
Labels: bug,topic:gui

### Godot version

v3.4.4.stable.official [419e713a2]

### System information

Fedora 36 - Linux 5.17.14-300.fc36.x86_64

### Issue description

When creating a new `FileDialog` node and change the mode to `OpenFile` or any other Open operation, the title of the dialog will not changed. If the dialog was changed to `Save` mode then the dialog will rename as intended.

### Steps to reproduce

Step 1. Create a new `FileDialog` node in an existing project or a new project (For demoing, a new project has been created)
![1](https://user-images.githubusercontent.com/60545346/174068232-99615b20-4481-4547-89ce-ab043902cd10.png)

Step 2. Click on the node to open the Inspector
![2](https://user-images.githubusercontent.com/60545346/174068470-ff2a3bb9-ae5c-44be-9e41-7768db0963b6.png)

Step 3. In the `FileDialog` section in the Inspector, change the value of `Mode` to any that said `Open` (Like `OpenFile`, `OpenFiles`, etc.)
![3](https://user-images.githubusercontent.com/60545346/174068599-3f021ec6-97ea-4121-b1ab-2d1e8b73000f.png)

Step 4. In the `WindowDialog` section of the Inspector, change the value of "Window Title" to anything.
![4](https://user-images.githubusercontent.com/60545346/174068735-3486b9b8-6703-4220-8a8b-d65de5921b33.png)

Step 5. To make sure the dialog will open on startup, create a new script in the root node and call `popup()` on the `FileDialog` node in the `_ready()` function (This is for demonstration purposes).
![5](https://user-images.githubusercontent.com/60545346/174068993-c3cd1446-24ac-4fa2-9a1a-7a89e1454436.png)

Step 6. Run the project, and the File Dialog title would still be the `Open...` instead of `Something Some...` like we've set in Step 4.
![6](https://user-images.githubusercontent.com/60545346/174069512-71f91b8a-ddad-4760-9220-36812178652f.png)


### Minimal reproduction project

And here's the project I've used for demonstration.
[aaaaaaaaaa.zip](https://github.com/godotengine/godot/files/8918807/aaaaaaaaaa.zip)
Repository: godot
Issue: Shader editor missing search in files
Labels: enhancement,topic:editor,topic:shaders

### Godot version

4.0 alpha 10

### System information

Linux Manjaro, Vulkan, Intel Kaby Lake

### Issue description

Shader editor can only search in current file. This is weird, considering script editor can (that's why I'm filing this as a bug)

Especially egregious after https://github.com/godotengine/godot/pull/60803 broke practically all shaders in my project.

### Steps to reproduce

N/A

### Minimal reproduction project

n/A
Repository: pytorch
Issue: Float and double tensors randomly initialized with the same seed get different values for size >= 16
Labels: triaged,module: random

### 🐛 Describe the bug

Hello, when randomly initializing with the same seed two size-n tensors with dtypes float and double, they get different values for n >= 16. For n <= 15 they are equal as expected.

### Sample code to reproduce the problem
```python
import torch

n = 16
t1 = torch.zeros(n, dtype=torch.float)
t2 = torch.zeros(n, dtype=torch.double)

torch.manual_seed(0)
t1.normal_(0, 1)
torch.manual_seed(0)
t2.normal_(0, 1)

print(t1)
print(t2)
```

### Expected result
`t1` and `t2` should contain the same values.

### Obtained result
`t1` and `t2` have different values for n >= 16. For example with n=16:
```python
tensor([-1.1258, -1.1524, -0.2506, -0.4339,  0.8487,  0.6920, -0.3160, -2.1152,
         0.3223, -1.2633,  0.3500,  0.3081,  0.1198,  1.2377,  1.1168, -0.2473])
tensor([-2.3104, -0.3733, -1.0608,  0.9995, -0.8840, -1.2755, -0.6232, -0.8664,
        -1.2956,  1.5236,  0.3237,  2.0177,  1.1357, -1.2269,  0.0714,  0.3380],
       dtype=torch.float64)
```
`t1` and `t2` have equal values for n <= 15. For example with n=15:
```python
tensor([ 1.5410, -0.2934, -2.1788,  0.5684, -1.0845, -1.3986,  0.4033,  0.8380,
        -0.7193, -0.4033, -0.5966,  0.1820, -0.8567,  1.1006, -1.0712])
tensor([ 1.5410, -0.2934, -2.1788,  0.5684, -1.0845, -1.3986,  0.4033,  0.8380,
        -0.7193, -0.4033, -0.5966,  0.1820, -0.8567,  1.1006, -1.0712],
       dtype=torch.float64)
```

### Versions

```
Collecting environment information...
PyTorch version: 1.11.0.post2
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.3 LTS (x86_64)
GCC version: (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Clang version: 10.0.0-4ubuntu1 
CMake version: Could not collect
Libc version: glibc-2.31

Python version: 3.10.5 | packaged by conda-forge | (main, Jun 14 2022, 07:06:46) [GCC 10.3.0] (64-bit runtime)
Python platform: Linux-5.14.0-1042-oem-x86_64-with-glibc2.31
Is CUDA available: False
CUDA runtime version: No CUDA
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] numpy==1.22.4
[pip3] torch==1.11.0.post2
[conda] libblas                   3.9.0            15_linux64_mkl    conda-forge
[conda] libcblas                  3.9.0            15_linux64_mkl    conda-forge
[conda] liblapack                 3.9.0            15_linux64_mkl    conda-forge
[conda] mkl                       2022.1.0           h84fe81f_915    conda-forge
[conda] numpy                     1.22.4          py310h4ef5377_0    conda-forge
[conda] pytorch                   1.11.0          cpu_py310h75c9ab6_2    conda-forge
```

cc @pbelevich
Repository: material-ui
Issue: Accessibility of Tooltip with disabled items
Labels: new feature,accessibility,component: tooltip

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

I'm having trouble figuring out how to make accessibility work well with a Tooltip with disabled items.

If I follow [the docs](https://mui.com/material-ui/react-tooltip/#disabled-elements):

```jsx
<Tooltip title="Delete">
  <span>
    <IconButton disabled>
      <DeleteIcon />
    </IconButton>
  </span>
</Tooltip>
```

then Tooltip adds the label to the span instead of the button, and I get warnings from accessibility tools like Axe and Lighthouse that a span element probably shouldn't have an `aria-label` and that the button doesn't have an `aria-label`.

I can address the second issue by duplicating the label:

```jsx
<Tooltip title="Delete">
  <span>
    <IconButton aria-label="Delete" disabled>
      <DeleteIcon />
    </IconButton>
  </span>
</Tooltip>
```

But then I'm having to duplicate text, and I have two elements with the same label, which may introduce other accessibility concerns. (For example, React Testing Library's `screen.findByLabelText` is no longer happy, and I assume some screen readers would read it twice.)

Is there a clean way of fixing this? The only solution I can think of is for Tooltip to add some sort of `wrap` or `allowDisabled` or `WrapperComponent` prop that would cause it to use a `span` wrapper itself; that way, it could know the "real" child and inject the label or description there, while still having the wrapper it needs to let it work with a disabled child.

### Examples 🌈

See https://codesandbox.io/s/lucid-sound-oh0mnx?file=/src/App.tsx for an example.

### Motivation 🔦

See above.
Repository: pytorch
Issue: gradgradcheck fails for torch.native_layer_norm
Labels: module: double backwards,module: autograd,triaged

### 🐛 Describe the bug

gradgradcheck fails when `weights=None` and bias is defined for `torch.native_layer_norm`.
```python
import torch
from torch.autograd.gradcheck import gradgradcheck

a = torch.randn(2, requires_grad=True, dtype=torch.float64)
bias = torch.randn(2, requires_grad=True, dtype=torch.float64)

def func(a, bias):
    return torch.native_layer_norm(a, (2,), None, bias, 1e-5)

gradgradcheck(func, [a, bias])
```
```py
GradcheckError: Jacobian mismatch for output 1 with respect to input 2,
numerical:tensor([[1.0000, 0.0000],
        [0.0000, 1.0000]], dtype=torch.float64)
analytical:tensor([[0., 0.],
        [0., 0.]], dtype=torch.float64)
```

### Versions

Fails on Colab (1.11.0+cu113) and master branch.

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7
Repository: excalidraw
Issue: Feature Request: Scenes reorder
Labels: Excalidraw+

Would it be possible to reorder the Scenes in the Collection?
They are now ordered by the creation date, but I would like to reorder them afterwards.
Repository: tensorflow
Issue: Wrong is_gpu flag computation in graph_memory.cc
Labels: type:bug,comp:core,TF 2.9

<details><summary>Click to expand!</summary> 
 
 ### Issue Type

Bug

### Source

source

### Tensorflow Version

tf 2.9.1

### Custom Code

No

### OS Platform and Distribution

_No response_

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/Compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current Behaviour?

I work for Sonar and as part of our internal tests, we run our static analyzers on multiple open source codes. While reviewing our tests we saw the following code that is almost certainly not intended:
On the following line: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/core/grappler/costs/graph_memory.cc#L175
the method `std::string::find` will return `std::string::npos` if the searched substring is not present. Because `std::string::npos` is different from 0, casting `std::string::find` as a boolean does not return what one would expect and there is no way the test on this line returns anything other than true, whether there is a GPU or not.


### Standalone code to reproduce the issue

I don't know how this bug impacts the functional behavior of the tool. It might be completely innocuous, given its age.
I am also unsure whether it should be fixed by removing the flag altogether to keep the current years-old behavior or fixed to actually handle non-GPU devices.


### Relevant log output

_No response_</details>
Repository: rust
Issue: compile-time regression from switch from num_cpus to available_parallelism needs a regression test
Labels: E-needs-test,T-compiler

#97549 flagged a regression injected by PR https://github.com/rust-lang/rust/pull/94524

The problem was fixed by https://github.com/rust-lang/rust/pull/97911, but we should try to put a test in *somewhere* that catches if something similar crops up again.

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":null}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: pytorch
Issue: ONEDNN testing is not done properly in quantization codebase
Labels: oncall: quantization,triaged

Update: we have various tests in quantization which assume fbgemm but do not guard for fbgemm properly. We should change

```
@skipIfNoFBGEMM
def test_foo(...):
   ...
```

to 

```
@skipIfNoFBGEMM
def test_foo(...):
    with override_qengines('fbgemm'):
        ...
```


### 🐛 Describe the bug

When I run 

```
python test/test_quantization.py -k Fx
```

on master (revision c6c207f620d01c02f192613c5a231f2581dc3997), there are test failures. There should be no test failures.

Log of failures: https://gist.github.com/vkuzo/d33ce5313b2ac2180064a5a55b9093a2

### Versions

https://gist.github.com/vkuzo/f5683a595a1481aac892e3c300de3acd

cc @jerryzh168 @jianyuh @raghuramank100 @jamesr66a @jgong5 @Xia-Weiwen @leslie-fang-intel @vkuzo
Repository: TypeScript
Issue: Extract to inner function drops narrowed type 
Labels: Suggestion,Experience Enhancement

# Bug Report

### 🔎 Search Terms

- refactor
- refactoring

### 🕗 Version & Regression Information

4.8.0-dev.20220616, not a regression 

### 💻 Code

```ts
function doThing(x: number | string) { 
    if (typeof x === 'string') {
        x.charCodeAt(0); // Run extract to inner function here
    }
}
```

### 🙁 Actual behavior

The resulting code is invalid:

```ts
function doThing(x: number | string) {
    if (typeof x === 'string') {
        newFunction();
    }

    function newFunction() {
        x.charCodeAt(0); // Error here: x is of type number | string
    }
}
```
### 🙂 Expected behavior

We either don't offer the refactoring in this case or we somehow pass the narrowed type to the function
Repository: pytorch
Issue: [FX] TypeError when tracing cat taking split's output as input
Labels: triaged,module: fx

### 🐛 Describe the bug

Hi,

Let's say I'd like to feed `cat` with `split`'s output and trace it :

```python
import torch
from torch.fx import symbolic_trace

class M(torch.nn.Module):
    def forward(self, x):
        y = torch.split(x, 4, 2)
        return torch.cat(y, 0)

m = M()
traced = symbolic_trace(m)
print(traced.graph)
```

When running this, I get a `TypeError` because the tracer causes `split` to output a `Proxy` object (as expected, thanks to FX), but `cat` currently needs a sequence of tensors :
```shell
TypeError: cat() received an invalid combination of arguments - got (Proxy, int), but expected one of:
 * (tuple of Tensors tensors, int dim, *, Tensor out)
 * (tuple of Tensors tensors, name dim, *, Tensor out)
```

IMO issue #34294 seems to be closely related to what we see here.

### Versions

PyTorch version: 1.11.0+cu102
Is debug build: False
CUDA used to build PyTorch: 10.2
ROCM used to build PyTorch: N/A

OS: Ubuntu 22.04 LTS (x86_64)
GCC version: (Ubuntu 11.2.0-19ubuntu1) 11.2.0
Clang version: 14.0.0-1ubuntu1
CMake version: version 3.22.1
Libc version: glibc-2.35

Python version: 3.10.4 (main, Apr  2 2022, 09:04:19) [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-5.15.0-37-generic-x86_64-with-glibc2.35
Is CUDA available: False
CUDA runtime version: No CUDA
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] numpy==1.21.5
[pip3] torch==1.11.0
[pip3] torch-tb-profiler==0.4.0
[pip3] torchdiffeq==0.2.3
[pip3] torchensemble==0.1.7
[pip3] torchtext==0.12.0
[pip3] torchvision==0.12.0
[conda] Could not collect

cc @ezyang @SherlockNoMad
Repository: PowerToys
Issue: Open a window on a monitor from which it was launched 
Labels: Idea-Enhancement,Product-FancyZones,Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

It was very useful if a window opens on a monitor from which application was launched by Start menu or from desktop.

### Scenario when this would be used?

1. Press application icon on main desktop then it opens there. 
2. Then press application icon on second desktop and it opens on second monitor.
3. And we have two windows on different monitors (desktops) without moving windows from on to other.

At the moment the new window opens where it is opened already or where it was opened last time. It is not productive for user.

### Supporting information

_No response_
Repository: react
Issue: Bug: `hidden` attribute does not accept string values
Labels: Type: Bug,Component: DOM,Status: Unconfirmed

<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 

```
 "react": "18.3.0-next-522f47345-20220614",
 "react-dom": "18.3.0-next-522f47345-20220614",
```  

## Steps To Reproduce

```jsx
<span hidden="until-found">Hello React<span>
```

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

https://codesandbox.io/s/headless-violet-ygn593

## The current behavior

React will turn hidden into a boolean attribute and removes "until-found":

![preview of the dom after react-dom rendered until-found](https://user-images.githubusercontent.com/4113649/174130287-c07a5d53-e31c-43b4-8925-84a1c3dbf18d.jpg)

## The expected behavior

React does not strip "until-found" to allow using [hidden-until-found in Chrome 102+](https://developer.chrome.com/articles/hidden-until-found/) for better SEO and accessibility.
Repository: pytorch
Issue: quantization: misleading backend config for linear_dynamic_fp16
Labels: oncall: quantization,triaged

### 🐛 Describe the bug

In the current native_backend_config_dict (https://pytorch.org/docs/master/quantization-backend-configuration.html), we have the following entry for linear:

```
{
  'pattern': <class 'torch.nn.modules.linear.Linear'>,
  'dtype_configs': [
    {
      'input_dtype': torch.quint8,
      'weight_dtype': torch.qint8,
      'bias_dtype': torch.float32,
      'output_dtype': torch.quint8,
    },
    {
      'input_dtype': torch.quint8,
      'weight_dtype': torch.qint8,
      'bias_dtype': torch.float32,
      'output_dtype': torch.float32,
      'is_dynamic': True,
    },
    {
      'input_dtype': torch.float16,
      'weight_dtype': torch.float16,
      'bias_dtype': torch.float32,
      'output_dtype': torch.float32,
      'is_dynamic': True,
    },
  ],
  'observation_type': ObservationType.OUTPUT_USE_DIFFERENT_OBSERVER_AS_INPUT,
  'root_module': <class 'torch.nn.modules.linear.Linear'>,
  'reference_quantized_module_for_root': <class 'torch.nn.quantized._reference.modules.linear.Linear'>,
  'qat_module': <class 'torch.nn.qat.modules.linear.Linear'>,
},
```

This is misleading because the `linear_dynamic_fp16` is only supported for fbgemm and not qnnpack.  Filing this issue to not forget about this.

### Versions

torch version: '1.13.0a0+git3acd9bb'
revision: c6c207f620d01c02f192613c5a231f2581dc3997

cc @jerryzh168 @jianyuh @raghuramank100 @jamesr66a @jgong5 @Xia-Weiwen @leslie-fang-intel @vkuzo
Repository: frp
Issue: [Feature Request] sctp
Labels: proposal

### Describe the feature request

Sctp is a common stream-based networking protocol on top of IP. It would be great, if - next to UDP and TCP - frp cloud support that.

### Describe alternatives you've considered

No alternatives available.

### Affected area

- [ ] Docs
- [ ] Installation
- [X] Performance and Scalability
- [ ] Security
- [ ] User Experience
- [ ] Test and Release
- [ ] Developer Infrastructure
- [X] Client Plugin
- [X] Server Plugin
- [ ] Extensions
- [ ] Others
Repository: deno
Issue: Performance degradation in deno 1.11.0
Labels: perf,web,needs investigation

I just noticed that deno 1.11.0 had a huge performance degradation. And that problem remains in 1.23.0.

Steps to reproduce:

```
$ git clone https://github.com/vslinko/deno-csv.git
$ cd deno-csv
$ gco benchmark-test
$ cd benchmarks
$ deno upgrade --version 1.10.3
$ make test-deno-csv-CSVReader
test-deno-csv-CSVReader
Read 500001 lines for 8.745 seconds
$ deno upgrade --version 1.11.0
$ make test-deno-csv-CSVReader
test-deno-csv-CSVReader
Read 500001 lines for 57.650 seconds
```

I think the cause might be in [the array destructurization in TextDecoder#decode](https://github.com/denoland/deno/pull/10805/files#diff-b3a759f63320020b99af869bf4847169acad9b8e8436373e8693976c29cc4a32R4237-R4245).
Repository: godot
Issue: Adding Sprite2D Tooltip Stuck On Screen
Labels: bug,topic:editor,topic:2d

### Godot version

4.0.dev 4bbe7f0b9

### System information

Windows 10, AMD 5700 XT GPU

### Issue description

Whenever I drag a texture from FileSystem across the 2D viewport, I see an "adding Sprite2D..." text along with the texture on the viewport. After I've dragged the texture into the texture slot of a Sprite2D, the "adding Sprite2D..." text and texture go away. However, If I do the same, but drag the texture into an export var slot for a CompressedTexture2D, the "adding Sprite2D..." texture and text do not go away.

I'm not quite sure how this happens.

![image](https://user-images.githubusercontent.com/55255197/174172320-f6c5c2d1-e8f7-4e1e-8ae1-c9763cf02e0e.png)


### Steps to reproduce

Set up any object with a script containing a line for a CompressedTexture2D export var.

`@export var sprite : CompressedTexture2D`

Drag a texture from FileSystem to the node's export var slot.

### Minimal reproduction project

[Simple Game.zip](https://github.com/godotengine/godot/files/8922700/Simple.Game.zip)