sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: `rustc` hangs on structure parameterised by lifetime and recursive trait.
Labels: A-trait-system,A-associated-items,T-compiler,C-bug,I-hang,T-types

`rustc 1.62.0 (a8314ef7d 2022-06-27)` stable hangs on the following snippet. Also seems to hang nightly/beta, and stuff further up the chain like rust-analyzer and clippy.

```rust
trait Recursive {
    type Recur: Recursive;
}

struct Commutes<'a, R: Recursive> {
    // so that 'a and R are used, doesn't seem important
    // can also be PhantomData<&'a R>
    _used: &'a R,

    // not related to infinite size: can be e.g. Option<Box<Commutes<...>>>
    hierarchy: Commutes<'a, <R as Recursive>::Recur>,
}

// not necessary, just for self-containment
fn main() {}
```

There is a genuine use-case for this pattern, but it is a bit involved. I am happy to help get this fixed, and thank you for the hard work developing the compiler! Suggestions for workarounds very welcome in the meantime.
Repository: vscode
Issue: support reveal in finder when focus terminal
Labels: help wanted,feature-request,terminal-shell-integration

terminal menu context:

![image](https://user-images.githubusercontent.com/41773861/178471062-5e5c1a9a-d622-4c98-9252-0264a8856819.png)

And shortcut:

```
{
    "key": "alt+cmd+r",
    "command": "revealFileInOS",
    "when": "terminalFocus"
},
```

@Tyriar
Repository: storybook
Issue: React Native crash immediately because storybook build-in with core-js polyfills (TypeError: finally is not a function)
Labels: bug,needs triage

**Describe the bug**

![image](https://user-images.githubusercontent.com/4661784/178581754-b3eee129-5970-4a52-8992-ff4d723c00db.png)


```tsx
Promise.resolve().finally(()=>{})  //  TypeError: Promise.resolve().finally is not a function. 
```

It happened because `core-js` polyfills broke JS environment (https://reactnative.dev/docs/javascript-environment)

![image](https://user-images.githubusercontent.com/95620376/178473673-e4ac7200-25c2-451b-9540-1efc201ad3a4.png)


**To Reproduce**

Repo: https://github.com/retyui/storybook-issues-18691

```sh
git clone https://github.com/retyui/storybook-issues-18691
cd storybook-issues-18691 
yarn # instal deps
yarn start # run metro bundler

yarn android # open app 
# or `yarn ios`
```

**System**

...

**Additional context**

...
Repository: godot
Issue: Function set_texture on mesh changes albedo perfectly, but Godot throws an error
Labels: bug,topic:core

### Godot version

4.0.alpha.11

### System information

Windows 10

### Issue description

The exact code is:
character_mesh.get_mesh().get("surface_1/material").set_texture("albedo_texture", texture)
The error message says that it the first argument in set_texture() should be an int and not a string, yet the onscreen result is the same as it is when the argument is set to 0. 

### Steps to reproduce

Have a mesh and try to change its albedo texture trough code with "albedo_texture", text you get from just clicking and dragging "albedo" from the editor. 

### Minimal reproduction project

_No response_
Repository: vue
Issue: How to better cooperate with Vuex and Vue Router in <script setup></script> in 2.7
Labels: 2.7,docs

### What problem does this feature solve?
Hello！How to better cooperate with Vuex and Vue Router in <script setup></script> in 2.7？

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: godot
Issue: Antialiasing property is ignored when rendering Line2D or Polygon2D
Labels: bug,topic:rendering,confirmed,topic:2d

### Godot version

4.0-alpha11

### System information

Linux 5.18.9-arch1-1, NVIDIA driver version 515.57, RTX 3060

### Issue description

Antialiasing properties of the `Line2D` and `Polygon2D` nodes are being ignored. They are not being sent to the `RenderingServer` when being drawn.

A side question: does MSAA or other project-level antialias settings affect the 2D renderer?

### Steps to reproduce

Add any `Line2D` or `Polygon2D`. Toggling the antialias property of them does not have any effect.

### Minimal reproduction project

_No response_
Repository: vscode
Issue: Render of fullscreen stopped working correctly with auto hidden taskbar on windows
Labels: bug,upstream,windows,electron,confirmed,upstream-issue-linked

Issue Type: <b>Bug</b>

Updated VS Code fails to render / restore fullscreen (F11) the first time I run it. It maximizes correctly only after I switch to other window and back to the VS Code window. It's really annoying.

Here is a screenshot when I run VS Code the first time (black color is my background):
![image](https://user-images.githubusercontent.com/12855743/178507973-78170cee-6e74-488c-8831-a86eb924939c.png)

VS Code version: Code 1.69.0 (92d25e35d9bf1a6b16f7d0758f25d48ace11e5b9, 2022-07-07T05:28:36.503Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz (8 x 1800)|
|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|
|Load (avg)|undefined|
|Memory (System)|7.92GB (2.40GB free)|
|Process Argv|--disable-extensions --crash-reporter-id 5b38bab1-dd40-49b2-b32c-618058bc07a2|
|Screen Reader|no|
|VM|0%|
</details>Extensions disabled<details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonvspyt551:30345470
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vscscmwlcmt:30465135
cppdebug:30492333
vscaat:30438848
vsclangdf:30486550

```

</details>

<!-- generated by issue reporter -->
Repository: pytorch
Issue: Incorrect results for mean or sum kernels on aarch64 when building with gcc-7
Labels: triaged,module: arm

## Issue description

Some aarch64 kernels produce wrong results when building with gcc-7 in native aarch64 environement.
Probably related to #47098 (presumably fixed in #47099 and then reverted in ##50389)

## Code example

The problem is reproducible by building with the following Dockerfile
```
FROM arm64v8/ubuntu:bionic

ENV DEBIAN_FRONTEND=noninteractive
RUN apt-get update && \
    apt-get install -y --no-install-recommends \
    gcc-7 \
    g++-7 \
    libstdc++-7-dev \
    make \
    cpp \
    python3.8 \
    python3.8-dev \
    python3-pip \
    git \
    curl \
    ssh \
    ca-certificates && \
    update-ca-certificates && \
    # Clean up
    apt-get autoremove -y && \
    apt-get clean -y && \
    rm -rf /var/lib/apt/lists/*

# Installing cmake from a GitHub release && \
RUN export CMAKE_VERSION="3.21.4" && \
    curl -L https://github.com/Kitware/CMake/releases/download/v${CMAKE_VERSION}/cmake-${CMAKE_VERSION}-linux-aarch64.sh -o cmake-${CMAKE_VERSION}-linux-aarch64.sh && \
    chmod +x cmake-${CMAKE_VERSION}-linux-aarch64.sh && \
    ./cmake-${CMAKE_VERSION}-linux-aarch64.sh --skip-license --prefix=/usr/local/

RUN git clone https://github.com/pytorch/pytorch.git -b v1.12.0 --recursive

WORKDIR /pytorch

RUN python3.8 -m pip install -U setuptools wheel pip && \
    python3.8 -m pip install pyyaml numpy typing_extensions
RUN USE_CUDA=0 \
    USE_CUDNN=0 \
    USE_MKLDNN=0 \
    USE_DISTRIBUTED=0 \
    USE_OPENMP=1 \
    USE_MAGMA=0 \
    USE_NCCL=0 \
    USE_FBGEMM=0 \
    CC=gcc-7 \
    CXX=g++-7 \
    python3.8 setup.py bdist_wheel
RUN python3.8 -m pip install dist/torch-*.whl

WORKDIR /
RUN python3.8 -c 'import torch; m=torch.ones(5,12); print(torch.mean(m,axis=1), torch.sum(m, axis=1))'
RUN python3.8 -mtorch.utils.collect_env
```

produces the following results:
```
tensor([0.8333, 0.8333, 0.8333, 0.8333, 0.8333]) # expecting tensor([1., 1., 1., 1., 1.])
tensor([10., 10., 10., 10., 10.]) # expecting tensor([12., 12., 12., 12., 12.])
```

## System Info
```
PyTorch version: 1.12.0a0+git67ece03
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: Ubuntu 18.04.6 LTS (aarch64)
GCC version: Could not collect
Clang version: Could not collect
CMake version: version 3.21.4
Libc version: glibc-2.27

Python version: 3.8.0 (default, Dec  9 2021, 17:53:27)  [GCC 8.4.0] (64-bit runtime)
Python platform: Linux-5.13.0-1031-aws-aarch64-with-glibc2.27
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.23.1
[pip3] torch==1.12.0a0+git67ece03
[conda] Could not collect
```

cc @malfet
Repository: PowerToys
Issue: Add grepWin to PowerToys plugins
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

I can use grepWin with fresh new PowerToys installation and upgrade grepwin along with PowerToys release.

### Scenario when this would be used?

When I wanna search some strings in some files.

### Supporting information

The project url is:
https://github.com/stefankueng/grepWin
It's useful and powerful. It has saved me lots of time and I use it everyday! I hope this can be a part of powertoys because this powertoys is heavely used by developers all across the world.
Repository: pytorch
Issue: Reductions on tensors larger than GPU memory
Labels: feature,module: cuda,triaged,needs research

### 🚀 The feature, motivation and pitch

I am interested in the ability to compute reductions on tensors larger than memory. For example:

```python
A = zeros(size=(100,100))
B = zeros(size=(10000000,100,100))
A.uniform_()
B.uniform_()
(A@B).min()
```

This falls under the scope of the concept of lazy computation. The output is a single integer, the input doesn't fit in GPU memory or CPU memory, but fits on disk. The data is juggled between disk, CPU and GPU based on whatever is available automatically.

Per this thread on dev-discuss, we were wondering if this is presently a capability to any extent with current backends: https://dev-discuss.pytorch.org/t/lazy-tensor-core/232/20

For example, perhaps computation on tensors larger than GPU memory for some reductions (but not this one - since the data is all random, it must be swapped to CPU RAM or disk) is currently possible on an existing backend.

cc @ngimel @wconstab 



### Alternatives

_No response_

### Additional context

_No response_
Repository: flutter
Issue: Floating action buttons can't be disabled
Labels: framework,f: material design,c: API break,P3,team-design,triaged-design

Disabled FABs aren't a thing in Material.

This will be a breaking change, with the proposed solution to conditionally show the FAB. If `onPressed` was null previously (indicating a false disabled state) it should now hide the floating action button.

- Documentation should be updated
- Both `FloatingActionButton` and `FAB` should be checked

Related issue: #76120
Repository: TypeScript
Issue: incorrect type using keyof and for..in
Labels: Suggestion,Awaiting More Feedback

# Bug Report

It's possible to declare a key variable as a `keyof` before a `for..in` loop with no errors (even with strict mode enabled), even though it takes on values outside of that type.

For example in the following code, `key` is able to have the type `keyof A` even though it takes on other values:

```typescript
interface A { x: string; }
interface B extends A { y: string; }

const b: B = { x: 'foo', y: 'bar' };
const a: A = b;

let key: keyof A;
for (key in a) { // <-- this line should be an error in my opinion
  if (key === 'x') {
    console.log('expected key', key);
  } else {
    // here `key` has type `never`
    console.log('unexpected key!', key);
  }
}
```

If you remove the `keyof A` type annotation, then `key` has the correct type `string`.

If you try using other incorrect types, such as `let key: 'z';` or `let key: number;` then the error `The left-hand side of a 'for...in' statement must be of type 'string' or 'any'. (2405)` correctly appears. So it seems wrong to me that only this particular incorrect type is allowed.

Also, this behavior disagrees with how the types of `Object.keys()` (discussed in [#12253](https://github.com/microsoft/TypeScript/pull/12253#issuecomment-263132208)) and `for..in` (discussed in [#12314](https://github.com/microsoft/TypeScript/issues/12314#issuecomment-261589864)) intentionally avoid the mistake of having `keyof` types.

### 🔎 Search Terms

keyof, for..in, key type

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about keyof and for..in

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?#code/JYOwLgpgTgZghgYwgAgILIN7IB4C5kDOYUoA5gNzIC+AUKJLIigELITaQgAmBamyAT3xESICtRo0EAexBFkAI3ysAvPzzIA5DGnTNAGkH5NCuFE3VyU2fLj50ahVZoAbCGGQBrCEK8-pMGhWOlDIABTeAsigyHAAlPwA9InIADwAtOnIYAAWwLwuoCgEOdIAri5ciihwIGxQUNKhMQC2UdIADqDAsjTI0YERPsgqo1rYmgkYff3IMnLSbgB0LtKkYZrsHRAIkFWRBn4CcVb9VGwuBCjTs8jJyDnQKAAGkc8PcLxgAtvIzyAQABu0GeM368wIiwgKzWGzKAOw212EH2PgAhIdIicZrRaEA)

### 💻 Code

```ts
interface A { x: string; }
interface B extends A { y: string; }

const b: B = { x: 'foo', y: 'bar' };
const a: A = b;

let key: keyof A;
for (key in a) { // <-- this line should be an error in my opinion
  if (key === 'x') {
    console.log('expected key', key);
  } else {
    // here `key` has type `never`
    console.log('unexpected key!', key);
  }
}
```

### 🙁 Actual behavior

`for (key in a) {` does not have a type error

### 🙂 Expected behavior

`for (key in a) {` should have the error `The left-hand side of a 'for...in' statement must be of type 'string' or 'any'. (2405)`, as it does for other incorrect types.
Repository: flutter
Issue: Support for Share Extension in iOS Flutter app
Labels: c: new feature,platform-ios,c: proposal,P2,team-ios,triaged-ios

<!-- 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

Today, sharing tools are used more and more every day and allow users of the application to interact with the application without having to open it, as is the case with Gmail, or Google Drive, which shows users a small part of the application.

| Gmail | Google Drive |
| -- | -- |
| ![IMG_625BDDFB9BD3-1](https://user-images.githubusercontent.com/708747/178554081-7cfc320a-c43c-4faf-ae37-c9955517ea6b.jpeg) | ![IMG_DE360702BB63-1](https://user-images.githubusercontent.com/708747/178554096-beb2f4a6-ef6b-4526-98e7-759236aad1e2.jpeg) |

Flutter has this feature on Android, by creating a new `Activity` with the permissions to receive the content it is easy to have the expected behaviour. **But on iOS this is not possible**, because you cannot create a new instance of Flutter inside a `ShareExtension`, hindering the user experience.

## Proposal

Create some additional package that allows to create a new instance of Flutter within `ShareExtension` that could be the same as the instance in `AppDelegate` or a lighter one, allowing developers to access all the advantages of Flutter within that workspace.
Repository: pytorch
Issue: JIT trace takes forever on a simple method
Labels: oncall: jit

### 🐛 Describe the bug

```python
import torch
import torch.utils.benchmark as bench

from torch import Tensor

device = torch.device("cuda" if torch.cuda.is_available() else "cpu")

input_size = [64, 16, 2048, 2048//16]

m1 = torch.randn(input_size, device=device, dtype=torch.bfloat16)
m2 = torch.randn(input_size, device=device, dtype=torch.bfloat16)

def _matmul_max_impl(m1: Tensor, m2: Tensor) -> tuple[Tensor, Tensor]:
    _LOW = -64000.0
    out_shape = m1.shape[:-1]
    max = torch.full(out_shape, _LOW, dtype=m1.dtype, device=m1.device)
    max_i = torch.full(
        out_shape, 0, dtype=torch.long, device=m1.device
    )

    for i in range(m1.size(-1)):  # dimension m
        m = torch.matmul(m1, m2[:, :, i, :].unsqueeze(-1)).squeeze(-1)
        increased = m > max
        max = torch.where(increased, m, max)
        max_i = torch.where(increased, i, max_i)
    
    return max, max_i


def custom_matmul_max(m1: Tensor, m2: Tensor) -> tuple[Tensor, Tensor]:
    return _matmul_max_impl(m1, m2)

traced_matmul_max = torch.jit.trace(custom_matmul_max, (m1, m2))
# this next call has not finished after 1h running on a single core of 5950X
# no GPU load
traced_matmul_max(m1, m2)
```

### Versions

PyTorch version: 1.12.0+cu116
Is debug build: False
CUDA used to build PyTorch: 11.6
ROCM used to build PyTorch: N/A

OS: Microsoft Windows 10 Pro
GCC version: Could not collect
Clang version: 13.0.0 (https://github.com/llvm/llvm-project.git d7b669b3a30345cfcdb2fde2af6f48aa4b94845d)
CMake version: version 3.22.22040401-MSVC_2
Libc version: N/A

Python version: 3.10.4 | packaged by conda-forge | (main, Mar 30 2022, 08:38:02) [MSC v.1916 64 bit (AMD64)] (64-bit runtime)
Python platform: Windows-10-10.0.19044-SP0
Is CUDA available: True
CUDA runtime version: 11.7.64
GPU models and configuration:
GPU 0: NVIDIA GeForce RTX 3090
GPU 1: NVIDIA GeForce RTX 3090

Nvidia driver version: 516.59
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] mypy-extensions==0.4.3
[pip3] numpy==1.22.3
[pip3] performer-pytorch==1.1.4
[pip3] torch==1.12.0+cu116
[pip3] torchaudio==0.12.0+cu116
[pip3] torchvision==0.13.0+cu116
[conda] numpy                     1.22.3                   pypi_0    pypi
[conda] performer-pytorch         1.1.4                    pypi_0    pypi
[conda] torch                     1.12.0+cu116             pypi_0    pypi
[conda] torchaudio                0.12.0+cu116             pypi_0    pypi
[conda] torchvision               0.13.0+cu116             pypi_0    pypi
Repository: godot
Issue: AnimationLibrary should use property list
Labels: enhancement,topic:animation

### Godot version

4.0.alpha11

### System information

Windows 10

### Issue description

AnimationLibrary currently writes its embedded animations as a raw dictionary. For example:
```
[sub_resource type="AnimationLibrary" id="AnimationLibrary_b837x"]
_data = {
"FirstPerson": SubResource("Animation_i6vx5"),
"LOOKDOWN": SubResource("Animation_imeok"),
"LOOKLEFT": SubResource("Animation_q2ljn"),
"LOOKRIGHT": SubResource("Animation_h5rxe"),
"LOOKUP": SubResource("Animation_jlvfe"),
"ThirdPerson": SubResource("Animation_2n88e")
}
```

This could cause some issues, for example, invalid dictionary members could be added.

### Steps to reproduce

1. Create a new AnimationLibrary.
2. Add animations to it.
3. Save as text resource

### Minimal reproduction project

_No response_
Repository: TypeScript
Issue: Use TS interface/types color for TS imports as well
Labels: Suggestion,Experience Enhancement

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
Could you color by default (or with a setting) Typescript imports of the same color they have when used? Or is it already achievable somehow by tweaking Themes?

For example here Tab is an `interface` but is colored as a general import.
![image](https://user-images.githubusercontent.com/36935593/178532277-e491ff87-f280-4d26-a9b1-6789c01889d9.png)

Later when `Tab` gets used it gets assigned the TS color.
![image](https://user-images.githubusercontent.com/36935593/178533226-4f6cda84-4d24-4fce-b2ad-22941bb5db88.png)

My request is to consider imports and usage the same "token" with regards of color. It would be way easier to spot at a glance to `imports` JS symbols from TS ones.
Repository: vscode
Issue: Git - opening file clears multiple selection in source-control window
Labels: bug,git

Issue Type: <b>Bug</b>

this is a regression in 1.69
- open a large git project on a remote machine via SSH
- make lots of changes in many large files
- open source-control panel
- select one file in the source-control panel, then quickly shift-click another file to select a range of files
- ...
- the first file eventually opens (it has to happen in this order, hence ssh & large files. if the first file opens _before_ the shift-click then this does not repro. causing high CPU usage on the remote machine can help to increase the repro window)
- the opening of the file causes the multiple-selection in the source-control window to be replaced with a single-file selection of the file that opened.

VS Code version: Code 1.69.0 (92d25e35d9bf1a6b16f7d0758f25d48ace11e5b9, 2022-07-07T05:28:36.503Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No
Remote OS version: Linux x64 5.10.102.1-microsoft-standard-WSL2

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz (6 x 2904)|
|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|
|Load (avg)|undefined|
|Memory (System)|47.66GB (19.01GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|

|Item|Value|
|---|---|
|Remote|WSL: CentOS7|
|OS|Linux x64 5.10.102.1-microsoft-standard-WSL2|
|CPUs|Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz (6 x 2904)|
|Memory (System)|37.34GB (18.07GB free)|
|VM|0%|
</details><details><summary>Extensions (10)</summary>

Extension|Author (truncated)|Version
---|---|---
remote-containers|ms-|0.241.3
remote-ssh|ms-|0.84.0
remote-ssh-edit|ms-|0.80.0
remote-wsl|ms-|0.66.3
vscode-database-client2|cwe|5.5.7
gitlens|eam|12.1.1
autoscrolldown|fox|1.2.1
cpptools|ms-|1.11.2
hexeditor|ms-|1.9.7
edit-with-shell|ryu|1.3.0


</details>
<!-- generated by issue reporter -->