sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: wrong overload resolved for `torch.mul(x, 4)` in `__torch_dispatch__`
Labels: triaged,module: __torch_dispatch__

### 🐛 Describe the bug

minimal repro

```python
import torch
class ElementwiseMulScalarIntModule(torch.nn.Module):
    def __init__(self):
        super().__init__()

    def forward(self, x):
        return torch.mul(x, 4)

class TrivTensor(torch.Tensor):
    @staticmethod
    def __new__(cls, elem, *, requires_grad=None):
        if requires_grad is None:
            return super().__new__(cls, elem)
        else:
            return cls._make_subclass(cls, elem, requires_grad)

    @classmethod
    def __torch_dispatch__(cls, func, _types, args=(), kwargs=None):
        print(func)
        for arg in args:
            if isinstance(arg, cls): continue
            print(arg, type(arg))


ElementwiseMulScalarIntModule()(TrivTensor(torch.randint(10, (3, 4))))

> aten.mul.Tensor
> 4 <class 'int'>
```

might be related to https://github.com/pytorch/pytorch/issues/77223

cc @Chillee @ezyang @zou3519 @albanD @samdow @silvasean @cathyzhyi @powderluv 

### Versions

PyTorch version: 1.12.0.dev20220511+cpu
Is debug build: False
CUDA used to build PyTorch: Could not collect
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.4 LTS (x86_64)
GCC version: (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Clang version: 10.0.0-4ubuntu1 
CMake version: version 3.21.2
Libc version: glibc-2.31

Python version: 3.8.10 (default, Mar 15 2022, 12:22:08)  [GCC 9.4.0] (64-bit runtime)
Python platform: Linux-5.13.0-40-generic-x86_64-with-glibc2.29
Is CUDA available: False
CUDA runtime version: Could not collect
GPU models and configuration: GPU 0: NVIDIA GeForce RTX 3080
Nvidia driver version: 510.39.01
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] numpy==1.22.3
[pip3] torch==1.12.0.dev20220511+cpu
[pip3] torchvision==0.13.0.dev20220511+cpu
[conda] No relevant packages
Repository: pytorch
Issue: Disable issue doesn't disable multiple dtypes correctly
Labels: module: ci,triaged

### 🐛 Describe the bug

I wanted to disable `test_ref_small_input_prod_cuda` and `test_ref_small_input__masked_prod_cuda`, but creating a disabling issue for them didn't actually stop the tests from running (there are int8, int16, and int32 variants for both). I ended up having to create 6 separate issues.


cc @seemethere @malfet @pytorch/pytorch-dev-infra
Repository: pytorch
Issue: DISABLED test_ddp_profiling_autograd_profiler (__main__.TestDistBackendWithSpawn)
Labels: oncall: distributed,module: flaky-tests,skipped

Platforms: linux

This test was disabled because it is failing in CI. See [recent examples](http://torch-ci.com/failure/test_ddp_profiling_autograd_profiler%2C%20TestDistBackendWithSpawn) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/6399576647).

Over the past 3 hours, it has been determined flaky in 1 workflow(s) with 1 red and 4 green.

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang
Repository: vscode
Issue: Support for updatable/async menus and submenus
Labels: feature-request,upstream,electron,menus,upstream-issue-linked

In Java extension, we often receive feedback from users that refactoring and source action features are missing even though these features exist under these menus. We're thinking if there is a way to improve feature discovery for them.

Currently, users must click on the editor's context menu "Refactoring..." and "Source Action..." to display the supported options, which is not visible to new users. To improve visibility, one suggestion is whether VS Code could automatically expand their submenus when the cursor hovers over them.

![image](https://user-images.githubusercontent.com/14052197/168006206-bade6fbb-3922-4f0d-91b1-bfd36b6295c5.png)
Repository: flutter
Issue: Clean-up: Remove unused template support from snippets tool
Labels: framework,d: api docs,P2,c: tech-debt,team-framework,triaged-framework

The code for API doc samples is no longer embedded in the doc comments. It now lives under `examples/api`. This allows us to simplify the [snippets](https://github.com/flutter/assets-for-api-docs/tree/master/packages/snippets) tool by removing support for templates from it. With the new way of hosting API samples under `examples/api`, templates are no longer used.
Repository: flutter
Issue: [Windows] Consider using LanguageFont to get font family from language.
Labels: platform-windows,c: proposal,a: desktop,P3,team-windows,triaged-windows

<!-- 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?
-->

As noted here:
[Typography in Windows Apps #languages](https://docs.microsoft.com/en-us/windows/apps/design/style/typography#languages)
We can use the [LanguageFont font-mapping APIs](https://docs.microsoft.com/en-us/uwp/api/Windows.Globalization.Fonts.LanguageFont) to get a recommended font family for a particular language.


## 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.
-->
Repository: storybook
Issue: "Show code" doesn't show ng-content content
Labels: bug,angular

**Describe the bug**
There is a reported issue about this: https://github.com/storybookjs/storybook/issues/2817
And it mentions my problem at the end but the issue is closed.

I've been using storybook with React before and didn't have any problems there. But now that I am using it with Angular I have problems with components that uses content projection with <ng-content></ng-content>.

I have found ways to show the ng-content as an argument in storybook, but the value written in ng-content is not shown in the "Show code" window.

**To Reproduce**

Let's take this simple component, a styled paragraph <paragraph> with the template:

```
<p>
  <ng-content></ng-content>
</p>
```

So I can use it like this <paragraph>Here is some text</paragraph>

The story I have for it looks like this:

```
export default {
  title: 'Paragraph',
  component: Paragraph,
} as Meta;

export const ParagraphStory: Story = (args) => ({
  template: `<paragraph>${args.content}</paragraph>`,
});
ParagraphStory.argTypes = {
  content: { control: 'text' },
};
ParagraphStory.args = { content: 'Some text to be shown in the paragraph' };
```

This story looks like this when rendered:

<img width="1062" alt="Screenshot 2022-05-12 at 09 37 34" src="https://user-images.githubusercontent.com/9605720/168017433-f31444be-db69-414b-bf4e-564d0b9507e5.png">

As you can see the argument control is working, you can input text and it is shown in the preview. But if you look at the "Show code" content then there is nothiing between the tags <paragraph></paragraph>.

I would like it to show

<paragraph>Some text to be shown in the paragraph</paragraph>

**System**
System:
    OS: macOS 11.6
    CPU: (8) x64 Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz
  Binaries:
    Node: 16.10.0 - ~/.nvm/versions/node/v16.10.0/bin/node
    npm: 7.24.0 - ~/.nvm/versions/node/v16.10.0/bin/npm
  Browsers:
    Chrome: 101.0.4951.64
    Edge: 101.0.1210.39
    Firefox: 98.0.2
    Safari: 14.1.2
  npmPackages:
    @storybook/addon-actions: ^6.3.10 => 6.3.10 
    @storybook/addon-essentials: ^6.3.10 => 6.3.10 
    @storybook/addon-links: ^6.3.10 => 6.3.10 
    @storybook/angular: ^6.3.10 => 6.3.10 
    @storybook/builder-webpack5: ^6.3.10 => 6.3.10 
    @storybook/manager-webpack5: ^6.3.10 => 6.3.10 

**Additional context**
Repository: flutter
Issue: [flutter_plugin_tools] Don't require version changes for `dev_dependencies`
Labels: team,p: tooling,package,team-ecosystem,P3,triaged-ecosystem

In https://github.com/flutter/plugins/pull/5703 the `publishable` check thought there needed to be a version change, because `pubspec.yaml` changed. However, the only changes were to `dev_dependencies`, which don't need to be published. Ideally we should teach the tooling to know that's okay so it doesn't need overriding. (It would require much deeper analysis than that tooling is currently doing though, so it may not be worth the effort for an edge case.)
Repository: ant-design
Issue: 在formList中使用shouldUpdate
Labels: Inactive

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/dong-tai-zeng-jian-qian-tao-zi-duan-antd-4-20-4-forked-etyzgt?file=/package.json:189-197)

### Steps to reproduce

增加一个list项，为Gender添加一个值，再为other，添加一个值，在改变Gender为other值，再为Customize Gender，添加一个值

### What is expected?

输出的表单值只有gender和Customize Gender

### What is actually happening?

输出的表单值只有gender和Customize Gender，还有other值

| Environment | Info |
| --- | --- |
| antd | 4.20.4 |
| React | ^16.14.0 |
| System | 无 |
| Browser | 无 |

---
在单纯的表单中使用，是正常的，只有在formList中使用就会发生这种情况

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: godot
Issue: 100% GPU load on empty scene
Labels: bug,discussion,topic:rendering,needs testing,performance

### Godot version

3.x (multiple), 4.x (multiple, "Compatibility" renderer)

### System information

Windows 7, Radeon RX 580, Adrenalin 21.5.2, GLES2/3

### Issue description

Empty scene in Godot 3.x/4.x "Compatibility" renderer with `opengl3` driver (it's happening for me since at least 3.2, and is still happening with 3.5) causes 100% GPU load. Adding a sensible `run/frame_delay_msec` prevents immediate GPU inferno (GPU still bursts to 100% every frame though), but also (obviously) induces stutter etc.

At first I thought that this might be a VSync issue, but no VSync setting (neither via Godot project settings nor GPU settings) helped. Manually checking the amount of rendered frames per sec suggests that VSync is indeed on.

It doesn't happen for Godot 4.x with the new renderers, FWIW.

### Steps to reproduce

create empty scene, run, watch how the GPU spews fire
Repository: material-ui
Issue: [Stepper] Hover effect is huge
Labels: bug 🐛,component: stepper

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

When hovering a stepper element, the hover effect is huge and "touches" the following element:


![image](https://user-images.githubusercontent.com/1368405/168063692-25080733-4508-45f4-86f3-3152bf90bf98.png)


### Expected behavior 🤔

Have less padding around the stepper element and maybe add more margin, so there is some room between the stepper and the following element.
Something like this:


![image](https://user-images.githubusercontent.com/1368405/168064270-04037549-5d28-4aa3-a013-a046fe8ce916.png)


### Steps to reproduce 🕹

Steps:

1. Go to this documentation page: https://mui.com/material-ui/react-stepper/#non-linear
2. Click on the stepper element (I changed the background for my screenshot, so you can better see the hover effect)

### Context 🔦

_No response_

### Your environment 🌎

Documentation demo
Repository: node
Issue: Odd behavior with asynchronous console I/O in REPL
Labels: repl

### Version

v16.15.0

### Platform

Microsoft Windows NT 10.0.19044.0 x64

### Subsystem

_No response_

### What steps will reproduce the bug?

1. Open the REPL.
2. Run `setTimeout(() => console.log('h'), 1000)` and wait for the timer to expire. The letter `h` will print where the cursor was, and push the cursor down to the line after the prompt.
3. Type another letter which results in autofill, such as `g`. This already looks somewhat broken, with the letter appearing a few columns to the left of the cursor.
4. Hit tab to autofill. This is even more broken, as autofill picks up from the cursor rather than from the first letter.
5. Hit backspace and watch the word magically fix itself, with a new prompt in the same line as the cursor.

### How often does it reproduce? Is there a required condition?

It always occurs when `console.log` is called asynchronously after the prompt is rendered. `process.stdout.write` also has somewhat odd behavior, but is noticeably less broken than `console.log`, possibly because of the lack of a newline character on the end.

### What is the expected behavior?

It should be consistent with `Promise.reject`:

```js
> Promise.reject('h')
Promise {
  <rejected> 'h',
  [Symbol(async_id_symbol)]: 96,
  [Symbol(trigger_async_id_symbol)]: 5,
  [Symbol(destroyed)]: { destroyed: false }
}
> Uncaught 'h'
>
```

Note that, although this does print `Uncaught 'h'` after the prompt, it then prints a new prompt immediately. With `setTimeout` and `console.log`, the new prompt isn't printed until backspace is pressed.

### What do you see instead?

After step 3:
![image](https://user-images.githubusercontent.com/25109429/168084744-bb936231-6320-49bc-9096-cbe37ab62eec.png)
After step 4:
![image](https://user-images.githubusercontent.com/25109429/168084848-964d6462-3475-4770-b8ba-8b072a8aac96.png)
After step 5:
![image](https://user-images.githubusercontent.com/25109429/168085109-cc19831a-9a95-48fd-a15f-dd4b64397d30.png)

### Additional information

Although I discovered this in v16.15.0, it also appears to happen in v14.19.2, v17.9.0, and v18.1.0.
Repository: angular
Issue: strictly-typed forms do not check CVAs or template bindings
Labels: area: forms,cross-cutting: types,P2,forms: strictly typed,canonical

### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

See the stackblitz below.

TL;DR even though we use a `FormControl<number>`, its value can be null, simply because the CVA of inputs of type number sets the value to null.

The strictly-typed forms are not very consistent, IMHO, regarding the type insurance they provide. For example:

- they force us to have nullable values just in case one calls `reset()`, which unfortunately sets the value to null, unless we explicitly use the option `initialValueIsDefault`. Even though, in my experience, calling `reset()` is extremely rare.
- they force us to have undefined-able values in form groups just in case one would disable a control, thus making its value absent of the form group's value. Disabling fields is more common in my experience than calling `reset()`, but still quite rare.

But on the other hand:
- they don't care at all if the CVA used to set the control's value sets it to null (like in the example in the stackblitz). Using number inputs, or select boxes with a default null option, for example, is extremely common in my experience. And in that case, the non-nullability of the FormControl is a lie.

I would expect more consistency:
- either forms are paranoid, and don't ever let the typing lie, but in that case, a form control initialized with the `initialValueIsDefault` option and a non null initial value should check that its value is never set to null and throw if it's the case (like in the provided example)
- or forms should give the control of the type to the developer: if they know that they never call reset(), and that they never disable a control, and that the CVA never sets the value to null, then let them choose the type they want, and too bad for them if they screwed up (i.e. basically what happens every type you do `http.get<Something>()`)


### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/angular-tjtyng-kz6zuz?file=src%2Fapp%2Fapp.module.ts,src%2Fapp%2Fapp.component.html,src%2Fapp%2Fapp.component.ts,package.json,src%2Fstyles.scss,angular.json,src%2Findex.html

### Please provide the exception or error you saw

```true
NA
```


### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular 14.0.0-rc.0
```


### Anything else?

_No response_
Repository: ant-design
Issue: Tree组件点击节点的时候能否触发一个带有selectedKeys, expandKeys参数的事件
Labels: Inactive

### What problem does this feature solve?

目前 onSelect 这个事件只有选中的时候会触发，取消选中的时候不会触发。


### What does the proposed API look like?

希望增加一个点击和取消点击的时候都能触发的事件，比如类似于 onClickItem={ (selectedKeys, expandKeys, nativeEvent) => {}} 这样的事件。
这样可以在点击和取消点击的时候都能做一些相关操作。

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: PowerToys
Issue: Add an option to sort apps jump lists
Labels: Idea-New PowerToy,Product-Tweak UI Design

### Description of the new feature / enhancement

Jump lists is a great feature of Windows but we need a tool to be able to sort pinned items easily.

### Scenario when this would be used?

If I would like to move a pinned item to the top of the list the only way to do it is to unpin all items and pin the item that we want on the top and readd all the items that were pinned before.

### Supporting information

_No response_
Repository: rust
Issue: Misleading error message when mistyped pattern matching in closure's argument
Labels: A-diagnostics,A-parser,A-closures,T-compiler

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.

If you cannot produce a minimal reproduction case (something that would work in
isolation), please provide the steps or even link to a repository that causes
the problematic output to occur.
-->

Given the following code: ([playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=aee5344af3e9eb717a5b02db6801707d))

```rust
fn main() {
    let _ =
        std::collections::HashMap::<String, i32>::new()
            .iter()
            .map(|(k, v | format!("{}->{}", k, v));
}
```

The current output is:

```
error: mismatched closing delimiter: `}`
 --> src/main.rs:5:17
  |
1 | fn main() {
  |           - closing delimiter possibly meant for this
...
5 |             .map(|(k, v | format!("{}->{}", k, v));
  |                 ^ unclosed delimiter
6 | }
  | ^ mismatched closing delimiter

error: expected one of `,` or `:`, found `;`
 --> src/main.rs:5:51
  |
5 |             .map(|(k, v | format!("{}->{}", k, v));
  |                                                   ^ expected one of `,` or `:`
```

<!-- The following is not always necessary. -->
Ideally the output should look like:

```
error: expected one of `)`, `,`, `@`, or `|`, found `=>`
 --> src/main.rs:5:24
5 |             .map(|(k, v | format!("{}->{}", k, v));
  |                   ^    -^
  |                   |    |
  |                   |    help: `)` may belong here
  |                   ^ unclosed delimiter
```

Almost like it currently does for a similar `match` mistype: ([playgroud](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=f2beb488739f577a0cf62c6915e9eca5))

```rust
fn main() {
    match (1, 2) {
        (k, v => 0
    }
}
```

Although I'd prefer if it is a single error message, not two, like currently:

```
error: expected one of `)`, `,`, `@`, or `|`, found `=>`
 --> src/main.rs:3:9
  |
3 |         (k, v => 0
  |         ^    -^^
  |         |    |
  |         |    help: `)` may belong here
  |         unclosed delimiter

error: expected one of `,`, `.`, `?`, `}`, or an operator, found `)`
 --> src/main.rs:4:5
  |
3 |         (k, v => 0
  |               --  - expected one of `,`, `.`, `?`, `}`, or an operator
  |               |
  |               while parsing the `match` arm starting here
4 |     }
  |     ^ unexpected token
```

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: material-ui
Issue: [Popover] Positioning overlap with anchorEl when opened near the bottom of the viewport
Labels: new feature,component: Popover

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

The popover overlaps the anchorEl.
![MUI Popover - current behavior](https://user-images.githubusercontent.com/97179941/168110373-1c973768-0cc9-4d18-958c-bbb9fe31a967.png)

### Expected behavior 🤔

The popover goes above the anchorEl.
![MUI Popover - expected behavior](https://user-images.githubusercontent.com/97179941/168110462-21ef393a-1d9e-4b27-92b7-dafa3b958a53.png)

### Steps to reproduce 🕹

This can be reproduced on the [Popover anchor playground](https://mui.com/material-ui/react-popover/#anchor-playground).

Steps:

1. Set the `anchorOrigin.vertical` property to `bottom`. The popover should now be opening below the anchorEl.
2. Scroll down so that the anchorEl is at the bottom of the viewport.
     1. Playing around with small scrolling adjustments near the bottom of the viewport yields multiple different popover positioning results, i.e. at the very bottom of the viewport, partially cut off by the bottom of the viewport, and a few pixels above the bottom of the viewport.
3. Click on the anchorEl to open the popover.


### Context 🔦

I am trying to implement a Menu where, when the menu is opened, the menu items are listed below the anchorEl. Additionally, when the user opens the menu near the bottom of the viewport, I would like the menu items to automatically adjust and open above the anchorEl, without overlapping it.

### Your environment 🌎

Environment info excluded since this issue is reproducible on the MUI popover anchor playground.
Repository: node
Issue: Nodejs fails to install due to Calling SRSetRestorePoint API on latest insider build 22616.100
Labels: windows,install

### Version

18.1.0

### Platform

Windows 11 22H2 Build 22616.100

### Subsystem

_No response_

### What steps will reproduce the bug?

Click on installer, it will say install was interrupted after hitting finish and not go further after setting install options 

### How often does it reproduce? Is there a required condition?

it's consistent

### What is the expected behavior?

It will install

### What do you see instead?

install was interrupted

### Additional information

Workaround:
open an administrative command prompt
msiexec -i node-v18.1.0-x64.msi MSIFASTINSTALL=1
This will allow it to install without attempting a restore point.