sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: high CPU% when changing screens/monitors
Labels: platform:windows,discussion,topic:rendering,needs testing,performance

### Godot version

4.0.2 release

### System information

OS: Win10 CPU:I7-7700K 4.2GHz GPU1: 3080TI GPU2: Intel HD 630

### Issue description

Switching main window from one monitor to another and back (different GPUs) causes permanently much higher CPU%

### Steps to reproduce

using `get_window().current_screen = #` change from
1. monitor 0 (3080TI)
to
2. monitor 1 (intel hd)
and back to
3. monitor 0 (3080TI)

profiling (in visual studio) showed a significant % increase in `VulkanContext::swap_buffers()` from step 1 to 3

variations of window settings (full/windowed/transparency/vsync) didnt seem to make (much) difference.

### Minimal reproduction project

[PRISM.zip](https://github.com/godotengine/godot/files/11439811/PRISM.zip)

a simple spinning pyramid that follows your cursor
problem primarily demo'ed by 
```
	await get_tree().create_timer(3.0).timeout
	get_window().current_screen = 1;
	await get_tree().create_timer(3.0).timeout
	get_window().current_screen = 0;
```
Repository: PowerToys
Issue: Custom sorting and grouping
Labels: Needs-Triage

### Description of the new feature / enhancement

Often, the sorting function provided by the explorer is not enough. For example, say I have a file named `<year>_<code>_<section><section#>_<subsection><subsection#>_<name>.<ext>`. I don't want to rename the files to achieve custom sorting. Now, I need to sort a lot of files of similar names using regex for the name and using other attributes such as modified date. That is sorting with two or more columns. If I can include the attributes (and/or other metaproperties), I can achieve a better sorting. 

For e.g. 

Sort with this

`<ISO 8601 modified date>_<some regex for code>_<section><section#>_<subsection><subsection#>_<name>.<ext>`

Here year is omitted.

Also, if I have a lot of files with numbers, I want to sort them numerically and not lexically. 


Also, for eg. say I have several movies. I somehow, using the API from TMDB managed to get the ratings of those movies and their genre. I have updated them in some property. Also, movies may have many parts like Harry Potter 1,2 etc. Now, first, I want to group these files using genre and regex of movie name (because the movies downloaded won't always follow a specific pattern for the file name) and then for each group, I want to sort by a combination of rating, movie part, and release year. 

### Scenario when this would be used?

Sorting and grouping files with a lot of combinations; not just the ones given by the explorer. 

### Supporting information

_No response_
Repository: stable-diffusion-webui
Issue: [Bug]: "Send to Inpaint" hides old mask without removing it
Labels: bug-report

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What happened?

When I inpaint an image and send the new image back to inpaint, the old masked area appears to be cleared, but is actually not. Hitting the "undo" button in the drawing area will cause the old mask to re-appear.
Trying to generate without doing this will include the previously masked area.

### Steps to reproduce the problem

1. Define a masked region 
2. Hit generate
3. Send new image to inpaint
4. Draw a new mask
5. The masked area will be "cleared"
6. Inpaint will include the old masked area


### What should have happened?

Img2Img happens on the new masked region and does not have the old mask.
OR
The old mask remains visible when the image is sent back to img2img

### Commit where the problem happens

5ab7f213

### What platforms do you use to access the UI ?

Windows

### What browsers do you use to access the UI ?

Brave

### Command Line Arguments

```Shell
xformers, no-half, no-half-vae, deepdanbooru
```


### List of extensions

"You can copy it at Extension tab"
how?

### Console logs

```Shell
Console is normal and does not have anything that would help
```


### Additional information

_No response_
Repository: material-ui
Issue: [Input][Joy]: Safari shows today's date if value is null
Labels: docs,component: text field,browser: Safari,package: joy-ui

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example:

Steps:

1. Use Chrome and go to the official [documentation](https://mui.com/joy-ui/react-input/#inner-html-input). Look how the input shows mm/dd/yyyy
2. Use safari and go to the same page. The input shows 05/10/2023



### Current behavior 😯

Misbehavior between Chrome and Safari. 

### Expected behavior 🤔

Safari should show mm/dd/yyyy. Right now the user can be confused that a date has already been input.

### Context 🔦

I did a simple form with a birthday field. A user told me that all users had the same birthday, and was today... I realized later on that it only happens on Safari. 

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: macOS 13.3
  Binaries:
    Node: 18.10.0 - /usr/local/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 8.19.2 - /usr/local/bin/npm
  Browsers:
    Chrome: 112.0.5615.137
    Edge: Not Found
    Firefox: 90.0.2
    Safari: 16.4
  npmPackages:
    @emotion/react: ^11.10.0 => 11.10.6 
    @emotion/styled: ^11.10.0 => 11.10.6 
    @mui/base:  5.0.0-alpha.119 
    @mui/core-downloads-tracker:  5.13.0 
    @mui/icons-material: ^5.10.2 => 5.11.11 
    @mui/joy: ^5.0.0-alpha.79 => 5.0.0-alpha.79 
    @mui/lab: ^5.0.0-alpha.96 => 5.0.0-alpha.121 
    @mui/material: ^5.13.0 => 5.13.0 
    @mui/private-theming:  5.12.3 
    @mui/styled-engine:  5.12.3 
    @mui/system:  5.12.3 
    @mui/types:  7.2.4 
    @mui/utils:  5.12.3 
    @mui/x-data-grid:  5.17.25 
    @mui/x-data-grid-pro: ^5.17.23 => 5.17.25 
    @mui/x-date-pickers: ^6.0.0 => 6.0.3 
    @mui/x-date-pickers-pro: ^6.0.0 => 6.0.3 
    @mui/x-license-pro:  5.17.12 
    @types/react:  18.2.0 
    react: ^18.2.0 => 18.2.0 
    react-dom: ^18.2.0 => 18.2.0 
    styled-components: ^5.3.5 => 5.3.6 
    typescript:  4.9.5 
```
</details>
Repository: tauri
Issue: [bug] The size of the webview does not change when the tauri app window changes size on MacOs
Labels: type: bug,platform: macOS,status: needs triage

### Describe the bug

When I use window management software like Magnet app on MacOs, the size of the webview does not change when I change the window size. It seems that this only happens on the height, and there is no problem with the width. How can I solve it? 

Also, I think Safari kernel is really hard to use, Tauri should give developers an option whether to use Chromium as webview, otherwise adaptation is also painful, developers may not care about increment of a dozen megabytes of software package at all.

### Reproduction

- On MacOs, init a Tauri app project
- Give it a run
- Change window size by Magnet or drag the window to top of the desktop to let the window be resized to max.

To demonstrate the issue: 

```JS
import { appWindow } from '@tauri-apps/api/window'

appWindow.onResized(async () => {
  let size = await appWindow.innerSize()
  console.log('app innerSize', { width: size.width, height: size.height })
})

window.onresize = () => {
  console.log('html innerSize', {
    width: window.innerWidth,
    height: window.innerHeight,
  })
}
```
When reisze the window by pulling window's frame, it works properly. Because the retina resolution, app's innerHeight - html's innerHeight * 2 always equal 44(title bar height)
```
[Log] @@@app innerSize – {width: 640, height: 2012} (main.tsx, line 15)
[Log] ***html innerSize – {width: 320, height: 984} (main.tsx, line 21)
```

But when change the size by magnet, or max the window by drag the window to top of desktop's menubar, the webview's size is incorrect.

```
[Log] ***html innerSize – {width: 1160, height: 816} (main.tsx, line 21)
[Log] @@@app innerSize – {width: 2320, height: 2054} (main.tsx, line 15)
```

Also notice the order of the logs printed is not correct .

### Expected behavior

_No response_

### Platform and versions

```text
My tauri version is 1.3.0, @tauri-apps/cli version is 1.3.1, safari version is 13.1.3.
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: transformers
Issue: Flaky Whisper PT-TF & PT-Flax Equivalence Test
Labels: WIP

### System Info

transformers 4.29.0 dev

### Who can help?

@ArthurZucker @sanchit-gandhi @ydshieh 

### Information

- [ ] The official example scripts
- [ ] My own modified scripts

### Tasks

- [ ] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [ ] My own task or dataset (give details below)

### Reproduction

Flaky test, so not reproducible. Example run where the error occurred: 

* https://app.circleci.com/pipelines/github/huggingface/transformers/64100/workflows/b4463c5d-b3dc-4b00-a7cd-19acd096cb07/jobs/792381
* https://app.circleci.com/pipelines/github/huggingface/transformers/64111/workflows/dc9092c4-0673-46c7-b89f-f805bc20128c/jobs/792557
* https://app.circleci.com/pipelines/github/huggingface/transformers/64230/workflows/e2d42ca4-f367-4a85-9054-a0ea99e49849/jobs/794534

Occasionally, the PT-TF and PT-Flax whisper equivalence test fails. The tolerance was increased in #23257 and #23288 but the reason for recent failures has not yet been found. 
 
### Expected behaviour

Equivalence tests reliably pass.
Repository: angular
Issue: iOS - Button Click is ignored when there is a dynamic view created based on a touch or mouse Event
Labels: area: core,iOS,state: needs more investigation

### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

This bug is only happening in iOS:

If a view is created through `*ngIf` or `ViewContainerRef.createEmbeddedView` based on an event listener to `touchstart` or other mouse events and there is a button outside of the dynamic view then this button need to be clicked twice in order for the click event to be fired.

A minimal reproduction example is this:

```
import { CommonModule } from '@angular/common';
import { bootstrapApplication } from '@angular/platform-browser';
import { Component } from '@angular/core';

@Component({
  selector: 'app-root',
  standalone: true,
  imports: [CommonModule],
  template: `
    <h1>Angular iOS Click Bug Demo</h1>
    <p> In all browsers clicking the 'Hello' button will trigger an alert immediately.</p>
    <p> But in iOS Safari two clicks are needed. However this only happens if the dynamic view inside the ngIf contains an interactive element.<p>
    <p> If you remove the click listener manually it will work.</p>
    <button (click)="alert('test')">Hello</button>
    <div *ngIf="active"><span (click)="alert('you clicked the span')">Some interactive element</span></div>
  `
})
export class AppComponent {
  active = false;
  alert = alert;

  constructor() {
      window.addEventListener('touchstart', () => this.setActive());
  }

  setActive() {
    if (!this.active) {
      this.active = true;
    }
  }
}


bootstrapApplication(AppComponent)
```

In this example the `Hello` button needs to be clicked twice in iOS. If you remove the (click) event from the span inside the dynamic view then the `Hello` button needs to be clicked only once

### Please provide a link to a minimal reproduction of the bug

https://github.com/jbchr/angular-ios-click-bug

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 16.0.0
Node: 16.20.0
Package Manager: npm 8.19.4
OS: darwin arm64

Angular: 16.0.0
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1600.0
@angular-devkit/build-angular   16.0.0
@angular-devkit/core            16.0.0
@angular-devkit/schematics      16.0.0
@schematics/angular             16.0.0
rxjs                            7.8.1
typescript                      5.0.4

But this is happening also at least from Angular V12
```


### Anything else?

_No response_
Repository: go
Issue: all: timeouts on `linux-s390x-ibm-race`
Labels: Builders,NeedsFix,arch-s390x

```
#!watchflakes
post <- builder == "linux-s390x-ibm-race" && (`test timed out` || `failed to start: context deadline exceeded` || `WaitDelay expired before I/O complete`)
```

(attn @golang/s390x)
Repository: pytorch
Issue: Tensor __getitem__ not documented, sparse grad?
Labels: module: sparse,triaged,module: advanced indexing

### 📚 The doc issue

I was search for some documentation on `Tensor.__getitem__` but I don't find any, at least not [here](https://pytorch.org/docs/stable/tensors.html#torch.Tensor). Maybe it is elsewhere?

Esp, I wonder if it uses `torch.gather` internally when you give it some scalar index.

And I wonder if it uses `sparse_grad` for `torch.gather` or not.

I also wonder, why does `torch.gather` has such a `sparse_grad` option at all? Why is it not always sparse? Why is the default to have it dense? What are the downsides in always enabling this? The [`torch.gather` documentation](https://pytorch.org/docs/stable/generated/torch.gather.html) doesn't really say anything about this.

If `Tensor.__getitem__` does not use `torch.gather`, is the gradient sparse or not?

E.g. when I have a tensor `x` of shape [T, B, F], and I loop over T, would it be a good idea to have this code (when training)?
```python
for t in range(T):
   y = f(x[t])
   ...
```
If `__getitem__` is not using sparse gradients, wouldn't it be better to have sparse gradients in this case? Wouldn't it always be better to have sparse gradients?


### Suggest a potential alternative/fix

Add some documentation on `Tensor.__getitem__`.

Extend the documentation of `torch.gather` `sparse_grad` option.

Briefly address my questions here.


cc @alexsamardzic @nikitaved @pearu @cpuhrsch @amjames @bhosmer
Repository: pytorch
Issue: torch.autograd.detect_anomaly should report the original forward trace as part of the error, rather than as out of band warning
Labels: module: autograd,triaged,actionable

### 🐛 Describe the bug

Today, when an exception is raised from a backward function, and anomaly mode was enabled, we will emit a warning saying what forward caused the exception:

```
/data/users/ezyang/a/pytorch/torch/autograd/__init__.py:319: UserWarning: Error detected in SumBackward0. Traceback of forward call that caused the error:                                                                                        
  File "/data/users/ezyang/a/pytorch/test/dynamo/test_misc.py", line 4872, in f                                          
    return h(a)                                                                                                          
 (Triggered internally at /data/users/ezyang/a/pytorch/torch/csrc/autograd/python_anomaly_mode.cpp:119.)                 
  result = Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass
```

There should be a way to force this information to instead get attached to the exception being thrown. This is important to do as high level error reporting frameworks will typically surface the exception message to the user, but not necessarily warnings (which have to be separately extracted from logs.)

### Versions

master

cc @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7
Repository: pytorch
Issue: Lazily format C++ stack trace if it is not used
Labels: module: performance,triaged

### 🐛 Describe the bug

Meta-only context: https://fb.workplace.com/groups/1405155842844877/?multi_permalinks=6965759763451096&hoisted_section_header_type=recently_seen

We can speed up stack trace collection by only formatting it when we actually need to print it. To do this, we can use @zdevito's new stack trace code described at https://dev-discuss.pytorch.org/t/fast-combined-c-python-torchscript-inductor-tracebacks/1158/3

This should speed up how quickly our test suite runs.

### Versions

master

cc @ngimel
Repository: create-react-app
Issue: Changelog react-app-polyfill 
Labels: needs triage

Hi team, don't find "Changelog" section for react-app-polyfill. Please help to clarify differences between versions 2 and 3. 
Share please some additional links if exist. Thanks
Repository: angular
Issue: Performance issue in Firefox with ng-container inside a <select>
Labels: area: core,core: ng-template and *microsyntax,core: performance,browser: firefox

### Which @angular/* package(s) are the source of the bug?

platform-browser

### Is this a regression?

No

### Description

I have a list of ~2000 entries (US Universities) in a `<select>` element, with some dynamic filtering done with an `ngIf`. In short the code looks like this:

```
    <select>
      <ng-container *ngFor="let option of options">
        <option
          *ngIf="true"
          [ngValue]="option.value"
        >
          {{ option.displayText ?? 'Please select' }}
        </option>
      </ng-container>
    </select>
```

While this works fine in Chrome, this causes Firefox to freeze. Spinning up the Firefox DevTools shows that the native DOM `Node.insertBefore` for each of the 2000 select items take almost 1s, compare to ~300ms in Chrome (x3000 faster).

Firefox:

<img width="1624" alt="Screenshot 2023-05-05 at 09 48 12" src="https://github.com/angular/angular/assets/2169585/9e817714-25e8-481f-a9de-f47ce39e7496">

Chrome:

<img width="1624" alt="Screenshot 2023-05-05 at 09 49 05" src="https://github.com/angular/angular/assets/2169585/8cfa6a87-1889-4f90-8e54-20c2cac52a90">

Playing around with the repro in https://stackblitz.com/edit/angular-f1vhwu?file=src%2Fmain.ts shows that removing the `*ngIf` & moving the `*ngFor` to the `<option>` element (aka removing the `<ng-container>`) works around the issue, although in my case I cannot do that (e.g. pre-filter the `options` object) as I use the `*ngIf` to handle select groups/items.

In addition, this issue seems to be specific to `<ng-container>`s inside `<select>` elements, as a simple list of `<div>`s load fine in Firefox (https://stackblitz.com/edit/angular-akq8zj?file=src/main.ts):

```
    <ng-container *ngFor="let option of options">
      <div *ngIf="true">
        {{ option.displayText ?? 'Please select' }}
      </div>
    </ng-container>
```

In short, there seem to be a performance bug specific to Firefox with the way Angular handles `<ng-container>` elements within `<select>`

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/angular-f1vhwu?file=src%2Fmain.ts

### Please provide the exception or error you saw

```true
Firefox becomes unresponsive and shows the "This page is slowing down Firefox.." banner
```


### Please provide the environment you discovered this bug in (run `ng version`)

```true
I'm on v14 but I've upgraded the StackBlitz to latest and it still happens
```


### Anything else?

Our CEO happens to be using Firefox 😀
Repository: pytorch
Issue: Sequence annotation in type hints is wrong
Labels: module: typing,triaged

### 🐛 Describe the bug

We have generated .pyi files that specify annotation of SymInt[], float[], and possibly other types as Sequence[T]:
```
// torch.ones in torch/_VF.pyi
def ones(size: Sequence[Union[_int, SymInt]], *, out: Optional[Tensor] = None, dtype: Op
tional[_dtype] = None, layout: Optional[_layout] = None, device: Optional[Union[_device,
 str, None]] = None, pin_memory: Optional[_bool] = False, requires_grad: Optional[_bool]
 = False) -> Tensor: ...
```
This is incorrect, because we only support Tuple and List via python_arg_parser (and Sequence represents anything that subscribes to the Sequence API, like ranges).

Some options are:
- we correct these annotations (probably the easiest option)
- we support PySequence in python_arg_parser (https://docs.python.org/3.8/c-api/sequence.html)

### Versions

main

cc @ezyang @malfet @rgommers @xuzhao9 @gramster
Repository: storybook
Issue: [Bug]: Accessibility violations
Labels: bug,ui,accessibility

### Describe the bug

Just wanted to mention - I just bumped a project I'm working on to Storybook 7 and I'm getting a lot of Axe accessibility violations. Most seem centered around color contrast (the document section labels have low contrast) and form `id`s not being unique. 

I checked the Create React App (TypeScript) base project from [Storybook.new](https://new-storybook.netlify.app) to make sure this wasn't something my team introduced and I'm getting the same accessibility violations there. 

It'd be great if Storybook were accessible out of the box.

### To Reproduce

You can find the accessibility bugs in the base Create React App (TypeScript) project via storybook.new. If you open this project in its own window and run an audit using an accessibility tool like Axe, you'll find errors around color contrast, unique `id`s, etc.

### System

```shell
I'm using MacOS + Chrome.
```


### Additional context

_No response_
Repository: rust
Issue: ICE: no errors encountered even though `delay_span_bug` issued
Labels: I-ICE,T-compiler,C-bug

<!--
Thank you for finding an Internal Compiler Error! 🧊  If possible, try to provide
a minimal verifiable example. You can read "Rust Bug Minimization Patterns" for
how to create smaller examples.
http://blog.pnkfx.org/blog/2019/11/18/rust-bug-minimization-patterns/
-->

### Code

```Rust
.route(
            "/panoramas/upload",
            put(upload_panorama_image)
                .route_layer(DefaultBodyLimit::disable())
                .route_layer(RequestBodyLimitLayer::new(10_485_760)),
        )
```

This code uses `axum`, `tower_http` ~~the features `error_in_core` and `try_trait_v2`~~.

~~I haven't been able to create a minimal verifiable example. I will continue trying and edit this issue.~~

```rust
use axum::{routing::put, Json, Router};
use tower_http::limit::RequestBodyLimitLayer;

async fn hello() -> Json<()> {
    Json(())
}

pub(crate) fn setup() -> Router<()> {
    Router::new()
        .route(
            "/",
            put(hello).layer(RequestBodyLimitLayer::new(10_485_760)),
        )
        .route(
            "/panoramas/upload",
            put(hello).route_layer(RequestBodyLimitLayer::new(10_485_760)),
        )
}

fn main() {}
```

I _think_ this is the minimal verifiable example.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.71.0-nightly (2f2c438dc 2023-05-08)
binary: rustc
commit-hash: 2f2c438dce75d8cc532c3baa849eeddc0901802c
commit-date: 2023-05-08
host: aarch64-apple-darwin
release: 1.71.0-nightly
LLVM version: 16.0.2
```

Fails on `2023-05-10`, `2023-05-01`, `2023-04-01` and stable.

### Error output

https://gist.github.com/indietyp/d291b4398294d37fbaf8b9e8cbf36cf2