sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: Installing PyTorch with BUILD_SPLIT_CUDA=ON and CUDNN fails on linker error
Labels: module: build,module: cudnn,module: cuda,triaged,actionable

### 🐛 Describe the bug

Environment:
OS: Fedora 36, x86_64
Device: GeForce RTX 3070 Mobile
GCC: 10
Cuda: 11.6

I tried to install PyTorch with the following command:
```
(pytorch10) DEBUG=0 USE_DISTRIBUTED=0 TORCH_CUDA_ARCH_LIST="8.6" BUILD_SPLIT_CUDA=ON USE_MKLDNN=0 USE_CUDA=1 BUILD_TEST=0 USE_FBGEMM=0 USE_OPENMP=0 BUILD_CAFFE2_OPS=0 BUILD_CAFFE2=0 USE_EXPERIMENTAL_CUDNN_V8_API=0 USE_NNPACK=0 USE_QNNPACK=0 USE_NCCL=0 USE_XNNPACK=0 CMAKE_CXX_COMPILER=/home/linuxbrew/.linuxbrew/bin/g++-10 CMAKE_C_COMPILER=/home/linuxbrew/.linuxbrew/bin/gcc-10 python setup.py develop
```

the script failed on linking :

```
[2206/2210] Linking CXX executable bin/torch_shm_manager
FAILED: bin/torch_shm_manager
:
undefined reference to `at::native::cudnn_batch_norm(at::Tensor const&, at::Tensor const&, c10::optional<at::Tensor> const&, c10::optional<at::Tensor> const&, c10::optional<at::Tensor> const&, bool, double, double)'
```

I installed CUDNN and it resolved the issue. I think instead there should be an error that this library is required before trying to create the cuda shared library. The symbol it complains about is a PyTorch symbol, not a CUDNN symbol.


### Versions

torch 1.14.0a0+git440f734

cc @malfet @seemethere @csarofeen @ptrblck @xwang233 @ngimel
Repository: pytorch
Issue: `chunk` a 0-dim tensor will crash in JIT script w/o profiling executor
Labels: oncall: jit

### 🐛 Describe the bug

`chunk` a 0-dim tensor will crash in JIT script w/o profiling executor

```py
import torch

class M(torch.nn.Module):
    def __init__(self):
        super().__init__()

    def forward(self, inp):
        fn_res = torch.chunk(inp, 1, dim=0)[0]
        return fn_res

fn = M().to('cpu')
inp = torch.rand([], dtype=torch.float32, device='cpu')


torch._C._jit_set_profiling_executor(False)
jit_fn = torch.jit.script(fn)
print(jit_fn.graph)
jit_fn(inp.clone())
```

```
segmentation fault (core dumped)
```

### Versions

```
Collecting environment information...
PyTorch version: 1.14.0.dev20221020
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.2.0-19ubuntu1) 11.2.0
Clang version: 14.0.0-1ubuntu1
CMake version: version 3.24.1
Libc version: glibc-2.35

Python version: 3.9.13 (main, Aug 25 2022, 23:26:10)  [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-5.19.5-051905-generic-x86_64-with-glibc2.35
Is CUDA available: True
CUDA runtime version: 11.6.124
GPU models and configuration: GPU 0: NVIDIA GeForce RTX 3060
Nvidia driver version: 515.76
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] functorch==0.2.1
[pip3] numpy==1.23.3
[pip3] torch==1.14.0.dev20221020
[pip3] torchaudio==0.14.0.dev20221020
[pip3] torchvision==0.15.0.dev20221020
[conda] _tflow_select             2.3.0                       mkl  
[conda] blas                      1.0                         mkl  
[conda] cudatoolkit               11.3.1               h2bc3f7f_2  
[conda] functorch                 0.2.1                    pypi_0    pypi
[conda] libblas                   3.9.0            12_linux64_mkl    conda-forge
[conda] libcblas                  3.9.0            12_linux64_mkl    conda-forge
[conda] liblapack                 3.9.0            12_linux64_mkl    conda-forge
[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.3                   pypi_0    pypi
[conda] numpy-base                1.23.1           py39ha15fc14_0  
[conda] pytorch                   1.14.0.dev20221020 py3.9_cuda11.6_cudnn8.3.2_0    pytorch-nightly
[conda] pytorch-cuda              11.6                 h867d48c_0    pytorch-nightly
[conda] pytorch-mutex             1.0                        cuda    pytorch-nightly
[conda] tensorflow-base           2.9.1           mkl_py39h353358b_0  
[conda] torchaudio                0.13.0.dev20220923+cu116          pypi_0    pypi
[conda] torchvision               0.14.0.dev20220923+cu116          pypi_0    pypi
```
Repository: godot
Issue: Changing a SpinBox's value by dragging does not respect Allow Greater and Allow Lesser flags
Labels: discussion,topic:editor,usability,topic:gui

### Godot version

v4.0.beta3.mono.official [01ae26d31]

### System information

Windows 10

### Issue description

When dragging a `SpinBox`'s arrows to change its value, the value is still clamped between the minimum and maximum values, regardless of whether or not the Allow Greater or Allow Lesser flags are set.

### Steps to reproduce

From a new project:

1. Create a scene with a `SpinBox` control in it.
2. Toggle the `SpinBox`'s Allow Greater and Allow Lesser flags.
3. Attempt to change the `SpinBox`'s value beyond the minimum or maximum by dragging.

From the repro project:

1. Run `control.tscn`.
2. Attempt to change the value of the `SpinBox` in the scene beyond the minimum or maximum by dragging.

### Minimal reproduction project

[SpinBox Drag Repro.zip](https://github.com/godotengine/godot/files/9833308/SpinBox.Drag.Repro.zip)
Repository: stable-diffusion-webui
Issue: [Bug]: install gets stuck on "Cloning Stable Diffusion into repositories\stable-diffusion..."
Labels: asking-for-help-with-local-system-issues

### Is there an existing issue for this?

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

### What happened?

When i start the webui-user.bat everything works fine until it gets to the step where it should clone the SD repos
Someone told me that running the batch file from cmd could fix this but it didnt work for me
I already tried letting it run over night and it didnt help

I had a problem before that where it couldnt find python and git but after setting the path in the file it worked

### Steps to reproduce the problem

1. Go to stable-diffusion-webui-master directory
2. doubleclick the webui-user.bat
3. wait until it gets to the cloning step


### What should have happened?

It should clone the repo and proceed with the installation

### Commit where the problem happens

_No response_

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

Windows

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

Google Chrome

### Command Line Arguments

```Shell
none
```


### Additional information, context and logs

Ive got a Win 10 PC with
Geforce 1060 6GB
32GB ram
Ryzen 5 2600x 3,6 GHz
Repository: node
Issue: FormData, Response, Request, and Headers have incorrect property descriptors
Labels: confirmed-bug,help wanted

### Version

v18.11.0

### Platform

Microsoft Windows NT 10.0.19043.0 x64

### Subsystem

_No response_

### What steps will reproduce the bug?

The property descriptors should match such that this test succeeds:

```js

for (const global of [
  'Headers',
  'Request',
  'Response',
  'FormData'
]) {
  const desc = Object.getOwnPropertyDescriptor(globalThis, global)
  
  assert.notStrictEqual(desc, undefined)
  assert.deepStrictEqual(desc.value, globalThis[global])
  assert.ok(desc.writable)
  assert.ok(!desc.enumerable)
  assert.ok(desc.configurable)
}
```

### How often does it reproduce? Is there a required condition?

_No response_

### What is the expected behavior?

the tests from above pass

### What do you see instead?

the descriptors are inconsistent with other environments

### Additional information

_No response_
Repository: storybook
Issue: [Bug]: ArgsTable does not show controls when story is referenced through {Template.title}
Labels: bug,needs triage

### Describe the bug

When using the `<ArgsTable>` DocBlock, the table itself will only show story-related controls when the story name is explicitly referenced as a magic string:

`button.stories.mdx`
```
import { Meta, Canvas, Story, ArgsTable } from "@storybook/addon-docs";
import { moduleMetadata } from "@storybook/angular";
import { ButtonModule } from "./button.module.ts";
import { ButtonComponent } from "./button.component.ts";
import { DefaultButton, IconButton } from "./button.stories.ts";

<Meta
  title="Components/Button"
  component={ButtonComponent}
  decorators={[
    moduleMetadata({
      imports: [ButtonModule],
    }),
  ]}
  parameters={{
    viewMode: "docs",
  }}
/>

## This ArgsTable is missing the controls

<Canvas withSource="open">
  <Story story={DefaultButton} height="80px"></Story>
</Canvas>

<ArgsTable story={DefaultButton.title} />

## This works in the expected way 

<Canvas withSource="open">
  <Story story={IconButton} name="Icon Button"></Story>
</Canvas>

<ArgsTable story="Icon Button" />
```

Expected behaviour: The DocBlock should resolve the story correctly, no matter if it's a string or passed by reference
Actual behaviour: Controls only show up when the Story name is provided as a string


### To Reproduce

```shell
Use https://github.com/andreaswissel/design-systems-workshop/tree/lab-4 and add mdx provided above
```


### System

```shell
Environment Info:

  System:
    OS: macOS 12.4
    CPU: (16) x64 Intel(R) Xeon(R) W-2140B CPU @ 3.20GHz
  Binaries:
    Node: 14.16.1 - ~/.nvm/versions/node/v14.16.1/bin/node
    Yarn: 1.22.17 - ~/.nvm/versions/node/v14.16.1/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v14.16.1/bin/npm
  Browsers:
    Firefox: 99.0
    Safari: 15.5
  npmPackages:
    @storybook/addon-actions: 6.5.10 => 6.5.10 
    @storybook/addon-essentials: 6.5.10 => 6.5.10 
    @storybook/addon-interactions: 6.5.10 => 6.5.10 
    @storybook/addon-links: 6.5.10 => 6.5.10 
    @storybook/angular: 6.5.10 => 6.5.10 
    @storybook/builder-webpack5: 6.5.10 => 6.5.10 
    @storybook/manager-webpack5: 6.5.10 => 6.5.10 
    @storybook/testing-library: 0.0.13 => 0.0.13
```


### Additional context

_No response_
Repository: go
Issue: x/mod/sumdb/note: documentation for key formats is incomplete
Labels: Documentation,NeedsInvestigation

The sumdb note documentation for key formats is incomplete. https://pkg.go.dev/golang.org/x/mod@v0.6.0/sumdb/note

The documentation states that `The standard implementation of a Verifier is constructed by NewVerifier starting from a verifier key, which is a plain text string of the form "<name>+<hash>+<keydata>". `

It appears that the hash is in hexadecimal, while the keydata is base64-encoded. I cannot find a description of this anywhere in the documentation. The documentation does say that the key hash is an unsigned 32 bit integer.

Also, the keydata is one byte of key type followed by the actual bytes of the key. The documentation does say this: `There is only one key type, Ed25519 with algorithm identifier 1. New key types may be introduced in the future as needed, although doing so will require deploying the new algorithms to all clients before starting to depend on them for signatures.`. I don't see anywhere in the documentation that says that this algorithm identifier is the first byte of the keydata.

Having this fully documented is useful when you have signatures produced in the sumdb note and key format, and you want to verify those signatures using a program written in another language.
Repository: storybook
Issue: 7.0.0-alpha.40: Illegal export statement in @mdx-js/react
Labels: bug,needs triage

### Describe the bug

With 7.0.0-alpha.40, Jest 26.6.3 complains:

```
● Test suite failed to run

    Jest encountered an unexpected token

    This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.

    By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/en/ecmascript-modules for how to enable it.
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/en/configuration.html

    Details:

    /path/to/my/repo/node_modules/@mdx-js/react/index.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){export {
                                                                                             ^^^^^^

    SyntaxError: Unexpected token 'export'

      at Runtime.createScriptFromCode (../../node_modules/jest-runtime/build/index.js:1350:14)
      at Object.<anonymous> (../../node_modules/@storybook/addon-docs/dist/cjs/DocsRenderer.js:16:15)
```

I have Babel configured to transpile a set of opt-in node modules using `babel.config.js` in my monorepo root and `rootMode: 'upward'` in my babel-jest config, and I have added `@mdx/react` to my opt-in list. Note that when I disable babel entirely, I receive a more straightforward error:

```
/path/to/my/repo/packages/jest-config/src/setupJest.js:2
    import { noisyTests } from './noisyTests';
    ^^^^^^

    SyntaxError: Cannot use import statement outside a module

      at Runtime.createScriptFromCode (../../node_modules/jest-runtime/build/index.js:1350:14)
```

A little `console.log` debugging shows that `requireModuleOrMock` is not passing an `options` argument to `requireModule` in `node_modules/jest-runtime/build/index.js`, so the babel transformer is being bypassed.
Repository: PowerToys
Issue: Better labeling for Keyboard Manager Remap of NumPad non 0-9 keys
Labels: Idea-Enhancement,Help Wanted,Product-Keyboard Shortcut Manager

### Description of the new feature / enhancement

The Keyboard Manager "Remap keys" function has remaps available for all the NumPad numbers (0-9), but there is one more NumPad key that is usually toggled with a NumLock key:  the NumPad '.' (decimal point) button.

Usually a NumLock toggle that turns OFF NumLock will allow that key to function as "Delete".  Unfortunately this one NumPad key has no listing in the "Remap keys" feature.  If you could add that remap, it would make the NumPad remap options complete.

### Scenario when this would be used?

I have a keyboard where the manufacturer has decided to make the NumPad keys numeric-only.  (No NumLock toggle key)  

For 30 years I've been using keyboards with a NumLock key that can toggle NumLock OFF.  That way I can use the standard NumPad placement for directional keys, etc.  (Home, End, PgUp, PgDn, etc. which are in standard placements on NumPads, but are in various non-standard placements elsewhere. Therefore my muscle memory is highly linked to the NumPad with NumLock toggled OFF.  With a standard NumLock toggled OFF, the decimal place '.' button on the NumPad acts as a Delete button.)  "Remap keys" is perfect for this remap purpose except for that one missing NumPad key remap option.

### Supporting information

_No response_
Repository: vscode
Issue: Splitting editor triggers two layouts of existing editor
Labels: debt,perf,workbench-editor-grid,grid-widget

While debugging markdown preview performance, I noticed that splitting editors triggers two relayout. The first seems to be canceled out by the second.

Repo:

1. Open an untitled text editor
2. Split it to the side

This triggers two calls to `.layout` on the original editor. The first one has the incorrect size while the second has the correct side:

<img width="751" alt="Screen Shot 2022-10-20 at 5 12 44 PM" src="https://user-images.githubusercontent.com/12821956/197082665-de38b862-3d1d-4110-8f1e-4f6a7be147b2.png">

The first once is caused by a call to [`relayout`](https://github.com/microsoft/vscode/blob/84a929b8b7ea25af7f2c5fb4e76b6a65028a7a6c/src/vs/base/browser/ui/splitview/splitview.ts#L1084), while the second comes from [`distributeViewSizes`](https://github.com/microsoft/vscode/blob/84a929b8b7ea25af7f2c5fb4e76b6a65028a7a6c/src/vs/base/browser/ui/splitview/splitview.ts#L1090)

In this case, I believe that the first call can be dropped (it has the wrong size anyways)

For webviews, each of these layouts takes around 20ms, which is a fairly large percentage of the webview opening flow

<img width="576" alt="Screen Shot 2022-10-20 at 5 16 16 PM" src="https://user-images.githubusercontent.com/12821956/197082863-890ec11c-23da-4aec-a53c-a7e68d0746cd.png">
Repository: stable-diffusion-webui
Issue: [Bug]: Images left in a temp folder C:\Users\username\AppData\Local\Temp
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?

founded 1,6 GB of spare images created by the UI in the folder C:\Users\username\AppData\Local\Temp

### Steps to reproduce the problem

i hope to be helpfull.

### What should have happened?

.

### Commit where the problem happens

_No response_

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

Windows

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

Brave

### Command Line Arguments

_No response_

### Additional information, context and logs

_No response_
Repository: pytorch
Issue: index_select() applied in sparse tensor can't backprop
Labels: module: sparse,triaged

### 🐛 Describe the bug

index_select() applied in sparse tensor can't backprop.

As the example below demostrates:
```
import torch

i = torch.tensor([[0, 1]])
v = torch.tensor([2., 2.], requires_grad=True)
s = torch.sparse_coo_tensor(i, v, size=[4], requires_grad=True)

print(s)
idx = torch.tensor([1, 2])
r = torch.index_select(s, 0, idx.detach()).to_dense()
print(r)
a = torch.sum(r)
a.backward()
print(v.grad)
```

When executed, it occurs an error:
```
Traceback (most recent call last):
  File "/home/xiahongchi/test/test.py", line 12, in <module>
    a.backward()
  File "/home/xiahongchi/anaconda3/envs/mininet/lib/python3.8/site-packages/torch/_tensor.py", line 396, in backward
    torch.autograd.backward(self, gradient, retain_graph, create_graph, inputs=inputs)
  File "/home/xiahongchi/anaconda3/envs/mininet/lib/python3.8/site-packages/torch/autograd/__init__.py", line 173, in backward
    Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass
RuntimeError: Tensors of type SparseTensorImpl do not have strides
```

### Versions

PyTorch version: 1.12.1+cu102
Is debug build: False
CUDA used to build PyTorch: 10.2
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: Could not collect
CMake version: version 3.16.3
Libc version: glibc-2.31

Python version: 3.8.13 (default, Mar 28 2022, 11:38:47)  [GCC 7.5.0] (64-bit runtime)
Python platform: Linux-5.15.0-48-generic-x86_64-with-glibc2.17
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
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] torch==1.12.1
[conda] torch                     1.12.1                   pypi_0    pypi

cc @nikitaved @pearu @cpuhrsch @amjames @bhosmer
Repository: stable-diffusion-webui
Issue: [Feature Request]: Saving Images/Grids: Max Filename Length
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 ?

limit the length a filename can have

### Proposed workflow

1. Go to Settings
2. Change the Max Filename Length

### Additional information

it would just be kind of useful, and there's already a max words for prompt_words in folder names, so limiting filenames has a precedent
Repository: opencv
Issue: cannot run the cv::namedWindow after compile (Mingw)
Labels: bug

### System Information

OpenCV version: 4.6.0
Operating System / Platform: Windows 10
Compiler & compiler version: g++ (Rev4, Built by MSYS2 project) 12.2.0

### Detailed description

> i already add my mingw bin to system enviroment value

The build is successful, but when I try to run the actual program, it doesn't work. This problem occurs when highgui code such as `cv::namedWindow` is inserted, and when the code is excluded, it runs successfully.

this is the error log when i debug the program.

```
[New Thread 29648.0x88c4]
[New Thread 29648.0x5d48]
[New Thread 29648.0x3a94]
[Thread 29648.0x5d48 exited with code 3221225781]
[Thread 29648.0x3a94 exited with code 3221225781]
[Thread 29648.0x654 exited with code 3221225781]
During startup program exited with code 0xc0000135.
```

### Steps to reproduce

the sample code.
```
#include <opencv2/opencv.hpp>
#include <iostream>

using namespace cv;
using namespace std;

int main(int argc, char **argv)
{
  cout << "Program Start" << endl;
  Mat image = imread("test.png");

  if (image.empty())
  {
    cout << "Could not open or find the image" << endl;
    return -1;
  }

  string windowName = "The Guitar";
  namedWindow(windowName);
  imshow(windowName, image);
  waitKey(0);
  destroyWindow(windowName);

  return 0;
}
```
the command line that i use to compile.
```
g++.exe -std=c++17 -ggdb3 -O3 -Wall -Werror -fdiagnostics-color=always -IC:/tools/msys64/mingw64/include -IC:/tools/msys64/mingw64/include/opencv4 -g main.cpp -o main.exe -lopencv_core -lopencv_imgproc -lopencv_imgcodecs -lopencv_highgui
```
when i run the code.
![image](https://user-images.githubusercontent.com/39794747/197113222-f2380461-9f8a-4e14-8540-12eb0851eaaa.png)

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)