sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Ctrl+Shift+Z action not triggering
Labels: bug,topic:input

### Godot version

4, Beta 14

### System information

Windows 10

### Issue description

Physical and non-physical `Ctrl+Shift+Z` does NOT work.
Physical and non-physical `Ctrl+Y` works

`ui_redo` is triggering with `Ctrl+Y` but not with `Ctrl+Shift+Z`
I tried to:
- Redefine the existing `Ctrl+Shift+Z` event. Note - it stayed non-physical.
- Delete the `Ctrl+Y` event
- Delete and create a new event with a `Ctrl+Shift+Z`. Note - it was created as physical.

PS. It works for the Godot editor itself, it doesn't work for a game.
### Steps to reproduce

Create a script that uses the action `Ctrl+Shift+Z`


### Minimal reproduction project
Currently both actions as Physical from my QWERTY layout.
Discovered while making this project. The action is used in the `main.gd`.
[DIY UndoRedo.zip](https://github.com/godotengine/godot/files/10479456/DIY.UndoRedo.zip)
Repository: PowerToys
Issue: Using a voting system for next utilities to add?
Labels: Needs-Triage

### Description of the new feature / enhancement

A lot of features suggested overlap in all the myriad of issues open.  I think a lot of ideas are lost/not visible.

e.g. I recently added information on using an existing open-source utility StExBar to add a name filter to the file explorer comment to a current issue: [Add an auto-filter row add-on to File Explorer](https://github.com/microsoft/PowerToys/issues/18916)

Have you considered consolidating ideas and opening a UserVoice-like voting system? I know it would take person power to do all this.

### Scenario when this would be used?

People could look at this before opening a new enhanecement

### Supporting information

_No response_
Repository: material-ui
Issue: Cannot read properties of undefined (reading '__emotion_styles')
Labels: package: styled-engine

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

_No response_

### Current behavior 😯

Hi team, when I am running my app, I am receiving following error which emerges from one of MUI files:

![image](https://user-images.githubusercontent.com/31355903/214039796-a5d548f2-c760-4bc8-a8a9-00fc29f7183e.png)

I am not able to reproduce it outside in codesandbox but putting it up here to check if there is anyone has idea why this might occur which I can look into. Any help here would be appreciated.

### Expected behavior 🤔

_No response_

### Context 🔦

_No response_

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
System:
    OS: Linux 3.10 Red Hat Enterprise Linux Server 7.9
  Binaries:
    Node: 16.18.1 
    Yarn: 1.22.11 
    npm: 7.23.0 
  Browsers:
    Chrome
  npmPackages:
    @emotion/react:  11.10.5 
    @emotion/styled:  11.10.5 
    @mui/base:  5.0.0-alpha.84 
    @mui/core-downloads-tracker:  5.11.5 
    @mui/icons-material:  5.11.0 
    @mui/lab:  5.0.0-alpha.87 
    @mui/material: ^5.1.0 => 5.11.5 
    @mui/private-theming:  5.11.2 
    @mui/styled-engine:  5.11.0 
    @mui/system:  5.11.5 
    @mui/types:  7.2.3 
    @mui/utils:  5.11.2 
    @mui/x-date-pickers:  5.0.0-alpha.1 
    @types/react:  18.0.27 
    react: ^17.0.0 => 17.0.2 
    react-dom: ^17.0.0 => 17.0.2 
    styled-components: 5.0.1 => 5.0.1 
    typescript: ^4.3.5 => 4.9.4 
```
</details>
Repository: next.js
Issue: Using i18n with beforeFiles is unpredictable
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.2.0: Fri Nov 11 02:03:51 PST 2022; root:xnu-8792.61.2~4/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.13.0
      npm: 8.19.3
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.1.4
      eslint-config-next: 13.0.6
      react: 18.2.0
      react-dom: 18.2.0

### Which area(s) of Next.js are affected? (leave empty if unsure)

Internationalization (i18n)

### Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/nextjs-i18n-issue-mrgkjh?file=%2Fnext.config.js

### To Reproduce

Define a `i18n` field in `next.config.js` as in the linked CodeSandbox or as described in  https://nextjs.org/docs/advanced-features/i18n-routing .

Try defining a rewrite in `beforeFiles` of the `next.config.js` such that any request to `/foo` goes to `/api/whatever` (in which case both are logically locale-less).

Now start your server and see that you cannot access `/foo` as it throws a `404`.

### Describe the Bug

tldr: It's all given in the reproduction description basically. 

It throws a `404` when defining a `rewrite` in `beforeFiles` in `next.config.js` when using a `i18n` definition and none of that is predictable / logical as per documentation.

### Expected Behavior

It should be very clear why this behaviour is happening - if it is intentional (nothing to be found here currently https://nextjs.org/docs/api-reference/next.config.js/rewrites).

Also, very important: I think conventions should be predictable otherwise they are not conventions (and writing rewrites sounds like something that should follow such conventions).

This means: I'd expect `afterFiles` to act the same way considering locale as `beforeFiles` as I would like both to be processing the same kind of routes - independent of their execution order.

### Which browser are you using? (if relevant)

not relevant

### How are you deploying your application? (if relevant)

not relevant
Repository: go
Issue: x/build: add a windows/arm builder using a windows/arm64 host
Labels: OS-Windows,Builders,NeedsFix,arch-arm

@zx2c4 windows/arm builder has been missing for a long time, although it still appears on the build dashboard.

I've been able to compile a windows/arm Go toolchain and run `go tool dist test` using a Windows ARM64 host by setting `GOHOSTARCH=arm` and `GOARCH=arm`. I believe that we could follow the same approach with the `host-windows11-arm64-azure` host (recently added as part of #53541), using it to run a windows/arm builder.

@heschi @thanm
Repository: vscode
Issue: Analyse RPC size data
Labels: telemetry,perf,engineering

follow-up from https://github.com/microsoft/vscode/issues/170955

We have added telemetry events to find heavy RPC messages (which freeze the renderer/EH when being parsed) and during February we should understand that telemetry and take action accordingly
Repository: next.js
Issue: CSP error when using next/image
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 21.6.0: Sun Nov  6 23:29:57 PST 2022; root:xnu-8020.240.14~1/RELEASE_ARM64_T8101
    Binaries:
      Node: 18.12.1
      npm: 9.3.1
      Yarn: 3.3.1
      pnpm: N/A
    Relevant packages:
      next: 13.1.5-canary.2
      eslint-config-next: 13.1.4
      react: 18.2.0
      react-dom: 18.2.0

### Which area(s) of Next.js are affected? (leave empty if unsure)

Image optimization (next/image, next/legacy/image)

### Link to the code that reproduces this issue

https://github.com/ennair/next-test/tree/next-image-test

### To Reproduce

1. Checkout the project.
2. Run yarn
3. Run yarn build
4. Run yarn start
5. Open localhost:3000
6. You will see the page loading with an image and in the console a CSP error.

### Describe the Bug

When using next/image it always adds inline styling on the image. It adds: style="color:transparent".
Also in case I add my own styling. Because of this, I get a CSP error. I have to add style-src 'unsafe-inline', which I do not want to add.

### Expected Behavior

Next/image should not add inline styling on the image component. 

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: stable-diffusion-webui
Issue: [Feature Request]: Naming the X/Y plot
Labels: enhancement

### Is there an existing issue for this?

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

### What would your feature do ?

![xy_grid-0162-1-1girl, portrait](https://user-images.githubusercontent.com/5646805/214077657-b6f2b54a-1533-4a6a-8aae-8af248f5029e.png)

1. Naming each X/Y plot grids.
2. It will be easier to remember the purpose of the experiment.
3. AI image creation research is accelerated.
4. Achieving world peace.

### Proposed workflow


![2023-01-24 002342](https://user-images.githubusercontent.com/5646805/214078940-a71debbd-af86-4075-98ab-d68e41643c04.png)

1. The user wants to use X/Y plot.
2. Entered both 'X/Y values' as usual.
3. Write 'Name' on it.
4. Press Generate.
5. The name is displayed in the upper left corner of the output grid image.

### Additional information

_No response_
Repository: pytorch
Issue: Segfault when running torch.atan2
Labels: triaged,module: complex

### 🐛 Describe the bug


Probably due to empty tensor:

```
import torch
import numpy as np
arg_1_tensor = torch.rand([], dtype=torch.float16)
arg_1 = arg_1_tensor.clone()
arg_2_tensor = torch.rand([3], dtype=torch.complex64)
arg_2 = arg_2_tensor.clone()
arg_3_tensor = torch.rand([3, 3, 3], dtype=torch.complex128)
arg_3 = arg_3_tensor.clone()
try:
  res = torch.atan2(arg_1,arg_2,out=arg_3,)
except Exception as e:
  print("Error:"+str(e))

```

Please note that this is a machine generated test cases (using fuzz testing). 

### Versions

```
PyTorch version: 1.13.1
Is debug build: False
CUDA used to build PyTorch: 10.2
ROCM used to build PyTorch: N/A

OS: Ubuntu 22.04.1 LTS (x86_64)
GCC version: (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
Clang version: Could not collect
CMake version: Could not collect
Libc version: glibc-2.35

Python version: 3.9.15 (main, Nov 24 2022, 14:31:59)  [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-5.15.0-58-generic-x86_64-with-glibc2.35
Is CUDA available: True
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: 
GPU models and configuration: GPU 0: NVIDIA GeForce GTX 1660 Ti
Nvidia driver version: 525.78.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.23.5
[pip3] torch==1.12.0
[pip3] torchaudio==0.12.0
[pip3] torchvision==0.13.0
[conda] blas                      1.0                         mkl  
[conda] cudatoolkit               10.2.89              hfd86e86_1  
[conda] ffmpeg                    4.3                  hf484d3e_0    pytorch
[conda] mkl                       2021.4.0           h06a4308_640  
[conda] mkl-service               2.4.0            py39h7f8727e_0  
[conda] mkl_fft                   1.3.1            py39hd3c417c_0  
[conda] mkl_random                1.2.2            py39h51133e4_0  
[conda] numpy                     1.23.5           py39h14f4228_0  
[conda] numpy-base                1.23.5           py39h31eccc5_0  
[conda] pytorch                   1.12.0          py3.9_cuda10.2_cudnn7.6.5_0    pytorch
[conda] pytorch-mutex             1.0                        cuda    pytorch
[conda] torchaudio                0.12.0               py39_cu102    pytorch
[conda] torchvision               0.13.0               py39_cu102    pytorch

```

cc @ezyang @anjali411 @dylanbespalko @mruberry @Lezcano @nikitaved
Repository: godot
Issue: Markers remain visible even if there are no open scenes.
Labels: bug,topic:editor,topic:2d

### Godot version

v3.5.2.rc2.official [1a2bf3eb4]

### System information

w10 64

### Issue description

Just watch the video.

https://user-images.githubusercontent.com/19652075/214095775-8377f819-351d-4c36-b808-c63fa7f6b911.mp4


### Steps to reproduce

See the video, simply close a scene with some nodes.

### Minimal reproduction project

...
Repository: pytorch
Issue: Ability to manually set the gradient in FSDP while inside `summon_full_params` and make it persistent
Labels: needs reproduction,oncall: distributed,triaged,module: fsdp

### 🚀 The feature, motivation and pitch

Hello, I'm working on training large models with Differential Privacy and I'm using PyTorch FSDP to avoid out of memory issues.

What I'm doing right now is having each gpu compute a sample gradient, clip it to a max norm and then summing it to a local variable. I would then like to reduce the local gradients across gpus by summing them together and then set this value to model's parameters `grad` attribute so that I can then call `optimizer.step()`.

My code basically looks like this:

        with FSDP.summon_full_params(model, with_grads=True):
            for i, param in enumerate(model.parameters()):
                if param.requires_grad:
                    all_params_grad = [torch.zeros_like(param.grad).to(rank) for _ in range(world_size)]
                    dist.all_gather(all_params_grad, params_grad[i].cuda())

                    # sum the gradients across the gpus
                    sum = torch.stack(all_params_grad).sum(0)

                    param.grad = sum.type(param.grad.type()).to(param.grad.device)

                    param.grad = privacy_engine.add_noise(param.grad) / batch_size

where `params_grad[i]` contains the local sum of the clipped sample gradients. The problem is that right after exiting the context, if I try to access the parameters grad values they will all be None and so taking a step won't update the model.

Is there a way to workaround this? Any help would really be appreciated!

### Alternatives

_No response_

### Additional context

_No response_

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu
Repository: go
Issue: x/pkgsite: links in package synopsis don't work in directory list
Labels: Thinking,pkgsite

### What is the URL of the page with the issue?

https://pkg.go.dev/mvdan.cc/sh/v3@v3.6.1-0.20230123163603-8b4fb75c77da#section-directories

### What is your user agent?

    Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/109.0

### Screenshot

![image](https://user-images.githubusercontent.com/3576549/214098022-baf37003-124b-4e06-a594-adf994735f08.png)

### What did you do?

Started using [doc links](https://go.dev/doc/comment#doclinks) in my godoc comments. Used a link to a package in another package's godoc.

### What did you expect to see?

The link to render properly in all relevant pkg.go.dev pages.

### What did you see instead?

It renders properly in the package itself: https://pkg.go.dev/mvdan.cc/sh/v3@v3.6.1-0.20230123163603-8b4fb75c77da/cmd/gosh

However, the link remains in its plaintext form in the directory view: https://pkg.go.dev/mvdan.cc/sh/v3@v3.6.1-0.20230123163603-8b4fb75c77da#section-directories
Repository: pytorch
Issue: segfault when running torch.igamma
Labels: triaged

### 🐛 Describe the bug


```
import torch
import numpy as np
arg_1_tensor = torch.randint(0,2,[], dtype=torch.bool)
arg_1 = arg_1_tensor.clone()
arg_2_tensor = torch.rand([3], dtype=torch.float32)
arg_2 = arg_2_tensor.clone()
arg_3_tensor = torch.neg(torch.rand([3, 3, 3], dtype=torch.float16))
arg_3 = arg_3_tensor.clone()
try:
  res = torch.igamma(arg_1,arg_2,out=arg_3,)
except Exception as e:
  print("Error:"+str(e))

```

### Versions

```
PyTorch version: 1.12.0
Is debug build: False
CUDA used to build PyTorch: 10.2
ROCM used to build PyTorch: N/A

OS: Ubuntu 22.04.1 LTS (x86_64)
GCC version: (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
Clang version: Could not collect
CMake version: Could not collect
Libc version: glibc-2.35

Python version: 3.9.15 (main, Nov 24 2022, 14:31:59)  [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-5.15.0-58-generic-x86_64-with-glibc2.35
Is CUDA available: True
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: 
GPU models and configuration: GPU 0: NVIDIA GeForce GTX 1660 Ti
Nvidia driver version: 525.78.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.23.5
[pip3] torch==1.12.0
[pip3] torchaudio==0.12.0
[pip3] torchvision==0.13.0
[conda] blas                      1.0                         mkl  
[conda] cudatoolkit               10.2.89              hfd86e86_1  
[conda] ffmpeg                    4.3                  hf484d3e_0    pytorch
[conda] mkl                       2021.4.0           h06a4308_640  
[conda] mkl-service               2.4.0            py39h7f8727e_0  
[conda] mkl_fft                   1.3.1            py39hd3c417c_0  
[conda] mkl_random                1.2.2            py39h51133e4_0  
[conda] numpy                     1.23.5           py39h14f4228_0  
[conda] numpy-base                1.23.5           py39h31eccc5_0  
[conda] pytorch                   1.12.0          py3.9_cuda10.2_cudnn7.6.5_0    pytorch
[conda] pytorch-mutex             1.0                        cuda    pytorch
[conda] torchaudio                0.12.0               py39_cu102    pytorch
[conda] torchvision               0.13.0               py39_cu102    pytorch
```
Repository: rust
Issue: `unused_parens` false positive with impl block
Labels: A-diagnostics,T-compiler,C-bug,L-unused_parens

### Code

```Rust
struct Something;
impl (<Something>::Item) {}
```

### Current output

```
warning: unnecessary parentheses around type
 --> src/lib.rs:2:6
  |
2 | impl (<Something>::Item) {}
  |      ^                 ^
  |
  = note: `#[warn(unused_parens)]` on by default
help: remove these parentheses
  |
2 - impl (<Something>::Item) {}
2 + impl <Something>::Item {}
  |

error[E0223]: ambiguous associated type
 --> src/lib.rs:2:7
  |
2 | impl (<Something>::Item) {}
  |       ^^^^^^^^^^^^^^^^^ help: use the fully-qualified path: `<Something as IntoIterator>::Item`

For more information about this error, try `rustc --explain E0223`.
warning: `playground` (lib) generated 1 warning
error: could not compile `playground` (lib) due to previous error; 1 warning emitted
```

on rustc nightly 2023-07-29

### Desired output

Same thing without the `unused_parens` warning.

### Rationale and extra context

Without the parentheses, it would be equivalent to
```rust
impl<Something> ::Item {}
```
Note that `Something` is now a generic type and `::Item` is a standalone item path.

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"StrayLittlePunk"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: pytorch
Issue: Double free when running torch.linalg.ldl_solve
Labels: triaged,module: edge cases

### 🐛 Describe the bug



```
import torch
import numpy as np
arg_1_tensor = torch.rand([5, 5], dtype=torch.float32)
arg_1 = arg_1_tensor.clone()
arg_2_tensor = torch.randint(-2048,8,[5], dtype=torch.int32)
arg_2 = arg_2_tensor.clone()
arg_3_tensor = torch.rand([5, 1], dtype=torch.float32)
arg_3 = arg_3_tensor.clone()
arg_4 = False
try:
  res = torch.linalg.ldl_solve(arg_1,arg_2,arg_3,hermitian=arg_4,)
except Exception as e:
  print("Error:"+str(e))

```

Log message:

```
double free or corruption (out)
Aborted

```

### Versions

```
PyTorch version: 1.13.1
Is debug build: False
CUDA used to build PyTorch: 11.6
ROCM used to build PyTorch: N/A

OS: Ubuntu 22.04.1 LTS (x86_64)
GCC version: (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
Clang version: Could not collect
CMake version: Could not collect
Libc version: glibc-2.35

Python version: 3.9.15 (main, Nov 24 2022, 14:31:59)  [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-5.15.0-58-generic-x86_64-with-glibc2.35
Is CUDA available: True
CUDA runtime version: 11.6.124
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA GeForce GTX 1660 Ti
Nvidia driver version: 525.78.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.23.5
[pip3] torch==1.13.1
[pip3] torchaudio==0.13.1
[pip3] torchvision==0.14.1
[conda] blas                      1.0                         mkl  
[conda] ffmpeg                    4.3                  hf484d3e_0    pytorch
[conda] mkl                       2021.4.0           h06a4308_640  
[conda] mkl-service               2.4.0            py39h7f8727e_0  
[conda] mkl_fft                   1.3.1            py39hd3c417c_0  
[conda] mkl_random                1.2.2            py39h51133e4_0  
[conda] numpy                     1.23.5           py39h14f4228_0  
[conda] numpy-base                1.23.5           py39h31eccc5_0  
[conda] pytorch                   1.13.1          py3.9_cuda11.6_cudnn8.3.2_0    pytorch
[conda] pytorch-cuda              11.6                 h867d48c_1    pytorch
[conda] pytorch-mutex             1.0                        cuda    pytorch
[conda] torchaudio                0.13.1               py39_cu116    pytorch
[conda] torchvision               0.14.1               py39_cu116    pytorch
```
Repository: godot
Issue: [Tracker] Vulkan error unable to create swapchain (device lost) happening randomly
Labels: bug,topic:rendering,confirmed,tracker

### Godot version

4.0 beta14 and earlier and likely later

### System information

Most users are on Windows, some on Linux,  variety of GPUs (intel, nVidia and AMD)

### Issue description

I am opening this tracker issue as a central place to track a bug that seems to be plaguing a variety of users. The bug occurs quite randomly, but appears to be most often connecting with complex shaders and/or updating uniforms. 

The bug leads to a freeze or crash when updating swap buffers along with the following errors:
```
E 0:00:01:0015   VulkanContext::swap_buffers: Condition "err" is true. Returning: ERR_CANT_CREATE
  <C++ Source>   drivers\vulkan\vulkan_context.cpp:2299 @ VulkanContext::swap_buffers()
E 0:00:01:0016   VulkanContext::prepare_buffers: Vulkan: Did not create swapchain successfully.
  <C++ Error>    Condition "err != VK_SUCCESS" is true. Breaking.
  <C++ Source>   drivers\vulkan\vulkan_context.cpp:2222 @ VulkanContext::prepare_buffers()
```

For some users these errors spam the console while the engine itself is frozen.

This issue is very difficult to debug as it is near impossible to reproduce reliably for people other than the affected users. 

```[tasklist]
- [ ] https://github.com/godotengine/godot/issues/71453
- [ ] https://github.com/godotengine/godot/issues/70946
- [ ] https://github.com/godotengine/godot/issues/69855
- [ ] https://github.com/godotengine/godot/issues/69046 (may not be connected as the issue went away with a driver update)
- [ ] https://github.com/godotengine/godot/issues/67404
- [ ] https://github.com/godotengine/godot/issues/59699
- [ ] https://github.com/godotengine/godot/issues/71841
- [ ] https://github.com/godotengine/godot/issues/60755
- [ ] https://github.com/godotengine/godot/issues/60979
- [ ] https://github.com/godotengine/godot/issues/52112
- [ ] https://github.com/godotengine/godot/issues/56856
- [ ] https://github.com/godotengine/godot/issues/74499
- [ ] https://github.com/godotengine/godot/issues/74554
- [ ] https://github.com/godotengine/godot/issues/74700
- [ ] https://github.com/godotengine/godot/issues/75659
```

### Steps to reproduce

Steps to reproduce can be found in individual reports

### Minimal reproduction project

See individual reports