sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: ipykernel crash importing torch after scipy in .ipynb file
Labels: needs reproduction,module: crash,triaged

### 🐛 Describe the bug

I'm working in a .ipynb notebook in VSCode on an Intel MacBook (late 2016 MBP)

Conda environment setup as:
```
% conda create --prefix ./envs/scipy
% conda activate ./envs/scipy
% conda install pytorch=1.12.1 -c pytorch
% conda install scipy
% conda install ipython ipykernel
```

As first cell in notebook, this causes kernel crash
```
from scipy.optimize import least_squares
import torch
```

This does not:
```
import torch
from scipy.optimize import least_squares
```

### Versions

Collecting environment information...
PyTorch version: 1.12.1
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 12.6 (x86_64)
GCC version: Could not collect
Clang version: 14.0.0 (clang-1400.0.29.102)
CMake version: Could not collect
Libc version: N/A

Python version: 3.10.6 (main, Oct  7 2022, 15:17:23) [Clang 12.0.0 ] (64-bit runtime)
Python platform: macOS-10.16-x86_64-i386-64bit
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] numpy==1.23.3
[pip3] torch==1.12.1
[conda] blas                      1.0                         mkl  
[conda] mkl                       2021.4.0           hecd8cb5_637  
[conda] mkl-service               2.4.0           py310hca72f7f_0  
[conda] mkl_fft                   1.3.1           py310hf879493_0  
[conda] mkl_random                1.2.2           py310hc081a56_0  
[conda] numpy                     1.23.3          py310hc1140d4_0  
[conda] numpy-base                1.23.3          py310h2a77c02_0  
[conda] pytorch                   1.12.1                 py3.10_0    pytorch
Repository: material-ui
Issue: [Select] `appears over` is also needed
Labels: new feature,component: select,package: material-ui

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

Just like the default behavior in v4

### Examples 🌈

now: https://mui.com/material-ui/react-select/
prefer: https://v4.mui.com/components/selects/

### Motivation 🔦

I quite agree with the following statement.
https://github.com/mui/material-ui/issues/18493#issuecomment-557793616
Whether `appear over` can be enabled through configuration?
For now, upgrading from v4, the default behavior is thoroughly different, and it's not fair to people who like `appear over`.
Repository: opencv
Issue: Why add this line before camera calibration?
Labels: category: calib3d,needs investigation

When I go through the code for camera calibration, I found this line changed the position of a marker in case `ASYMMETRIC_CIRCLES_GRID` board. If `CHESSBOARD` or `CIRCLES_GRID` used, it will change nothing. `ASYMMETRIC_CIRCLES_GRID` is different, before executing this line, the value of `objectPoints[0][s.boardSize.width - 1].x` should be 60, after this line, the value changed to 30, but it absolutely wrong.

It may suit `CHESSBOARD` and `CIRCLES_GRID` board, I mean, cause no errors, also no need. And it doesnot suit `ASYMMETRIC_CIRCLES_GRID` board at all. Is it a test code? or someting?

https://github.com/opencv/opencv/blob/e80b443cd93012f1fdd79baf7ed325beff606a89/samples/cpp/tutorial_code/calib3d/camera_calibration/camera_calibration.cpp#L566

![image](https://user-images.githubusercontent.com/7272659/197145527-22be37a0-b9cd-4540-9b06-f7367e440950.png)
Repository: opencv
Issue: VideoCapture.read() permanently stuck after reconnecting IP camera
Labels: bug

### System Information

OpenCV version: 4.6.0
Operating Systems / Platforms: both on Windows11 22H2 and Ubuntu 18.04.6
Python version: 3.9.7

### Detailed description

I'm trying to implement a way to reconnect a camera after connection has been lost but trying to grab/read a frame from an IP camera using RTSP gets permanently stuck if camera connection recovers while trying to connect to said camera.

Note: this also causes an abnormally high CPU usage ~20% on i5-11600.

### Steps to reproduce

Consider the following code:
```python
connected = False

while not connected:
	print("connecting to camera...")
	cap = cv2.VideoCapture(rtspURL)

	if cap.isOpened():
		connected = True
		print("connected")
	else:
		print("failed to connect, retrying...")

received, frame = cap.read()
print("frame received")
```

If I try to start a connection while the camera is offline, then if the camera goes back online before ```cap = cv2.VideoCapture(rtspURL)``` finishes executing, cap.isOpened() returns ```True``` yet when trying to call ```cap.read()``` it gets stuck forever with no way of recovering or having some sort of timeout.

### 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)
Repository: rust
Issue: Provide better errors and docs for conditional compilation of binaries
Labels: A-diagnostics,T-compiler

One of my Rust projects consists of a library and a binary. The library can be compiled to WASM but not the binary because one of the binary's dependencies does not support WASM compilation. I tried to disable compilation of the binary for WASM by putting the following attribute at the top-level of the `main.rs` file:

```rust
// main.rs

#![cfg(not(target_family = "wasm"))]
```

When compiling for WASM, the following error is thrown by the compiler:

```
error[E0601]: `main` function not found in crate `grex`
   --> src/main.rs:1:2
    |
1   | 
    |  ^ consider adding a `main` function to `src/main.rs`

```

It is not obvious how to handle this error and how to correctly do conditional compilation of binaries. It is not explicitly mentioned in the official Rust docs or I simply could not find it. The only trick that worked for me was to add a second `main()` function in the `main.rs` file which remains empty. When targeting WASM, this empty `main()` function is compiled, otherwise the original first one:

```rust
// main.rs

#[cfg(not(target_family = "wasm"))]
fn main() {
    // contains the binary-specific code
}

#[cfg(target_family = "wasm")]
fn main() {} // remains empty for the other targets
```

It would be great if the whole handling of conditional compilation of binaries could be improved. At least, the docs and compiler error message should be improved, stating that two separate conditionally compiled `main()` functions are needed if a binary cannot be compiled for all targets. It would be even better to support adding a top-level attribute such as 

```rust
#![cfg(not(target_family = "wasm"))]
``` 

to the `main.rs` file so that the binary is not compiled for WASM. Another alternative would be to provide a setting for it in the `Cargo.toml`, for instance.

Perhaps you will find ways for improvements in this matter. Thank you for your attention.
Repository: kubernetes
Issue: Crash in TestGetContainerOOMScoreAdjust
Labels: kind/bug,sig/node,kind/failing-test,needs-triage

### Which jobs are failing?

pkg/kubelet/qos

### Which tests are failing?

`TestGetContainerOOMScoreAdjust` in `pkg/kubelet/qos`
I transformed that testcase into a fuzz driver and tested it with [[go-fuzz](https://github.com/dvyukov/go-fuzz)](https://github.com/dvyukov/go-fuzz)
It crash with "integer divide by zero" when some argument related data are fuzzed.

### Since when has it been failing?

Always

### Testgrid link

_No response_

### Reason for failure (if possible)

_No response_

### Anything else we need to know?

Simplified PoC code is here:

```go
	test := oomTest{
		pod:             &cpuLimit,
		memoryCapacity:  0,
		lowOOMScoreAdj:  999,
		highOOMScoreAdj: 999,
	}
	GetContainerOOMScoreAdjust(test.pod, &test.pod.Spec.Containers[0], test.memoryCapacity)
```

and it crashed as:

```
panic: runtime error: integer divide by zero [recovered]
	panic: runtime error: integer divide by zero

goroutine 19 [running]:
testing.tRunner.func1.2({0xaf6ea0, 0x11714b0})
	/home/gogen/.local/go/src/testing/testing.go:1209 +0x24e
testing.tRunner.func1()
	/home/gogen/.local/go/src/testing/testing.go:1212 +0x218
panic({0xaf6ea0, 0x11714b0})
	/home/gogen/.local/go/src/runtime/panic.go:1038 +0x215
k8s.io/kubernetes/pkg/kubelet/qos.GetContainerOOMScoreAdjust(0x1179620, 0x11856e0, 0x0)
	/home/gogen/workspace/gowork/src/topproj/kubernetes/pkg/kubelet/qos/policy.go:63 +0x2d5
k8s.io/kubernetes/pkg/kubelet/qos.FuzzTestGetContainerOOMScoreAdjust({0xc000230400, 0x0, 0x200})
	/home/gogen/workspace/gowork/src/topproj/kubernetes/pkg/kubelet/qos/policy_test.go_TestGetContainerOOMScoreAdjust_test.go:79 +0x2b5
```

### 

### Relevant SIG(s)

/sig
Repository: PowerToys
Issue: Onenote Ruler useable anywhere.
Labels: Idea-Enhancement,Needs-Triage

### Description of the new feature / enhancement

The ruler in Onenote is a very useful tool to draw straigt lines with a pen (eg. surface pens) on touch devices (eg. surface ...).Especialy the adjustable angles are great. I love it but it's a pity as it's only availabe in onenote for Windows 10. It's so far not implemented in any other (windows) application like MS-Word.

I'd love to have a key shortcut that can open the ruler in any application or even the homescreen. 

<img width="1192" alt="ruler onenote" src="https://user-images.githubusercontent.com/76650047/197152324-3f0fd8de-c595-4c87-821a-7b6a744eecf9.png">


### Scenario when this would be used?

- Drawing in any application like MS-Word, notes, whiteboards and more. I guess it would be extremely useful. 

### Supporting information

_No response_
Repository: storybook
Issue: deprecated warning about "withActions" 
Labels: bug,needs triage

### Describe the bug

I've been using a combination of storybook + webcomponents, 
but it keeps triggering a warning when I configure actions via the officially recommended way.(https://storybook.js.org/docs/web-components/essentials/actions#action-event-handlers)
```js
export default {
  title: "desktop/button",
  component: "custom-button",
  argTypes: {
    id: { name: "id" },
    text: { name: "text" },

  },
  parameters: {
    actions: {
      handles: ["click"],
    },
  },
  
};
const template = (args) => {
  const button = new Button({...args});
  button.addEventListener("click", (event) => {
    console.log(event);
  });
  return button;
};

export const Base = template.bind({});
```
<img width="822" alt="截屏2022-10-19 16 15 17" src="https://user-images.githubusercontent.com/38276156/197147484-8e591cb4-7ca7-4802-afe7-5e27d70cb4b0.png">

The main.js
```js
module.exports = {
  "stories": ["../src/**/*.stories.@(js|jsx|ts|tsx)"],
  core: {
    builder: "webpack5",
  },
  addons: [
    "@storybook/addon-a11y",
    "@storybook/addon-viewport",
    "@storybook/addon-controls",
    "@storybook/addon-actions",
  ],
};
```
Then I try the official provided sample "npx storybook init --type react" to check react+storybook.
The same warning is fired after adding actions for the Button
```jsx
import { Button } from './Button';

// More on default export: https://storybook.js.org/docs/react/writing-stories/introduction#default-export
export default {
  title: 'Example/Button',
  component: Button,
  // More on argTypes: https://storybook.js.org/docs/react/api/argtypes
  argTypes: {
    backgroundColor: { control: 'color' },
  },
  parameters: {
    actions: {
      handles: ["click"],
    },
  },
};
```
<img width="1338" alt="截屏2022-10-21 17 23 13" src="https://user-images.githubusercontent.com/38276156/197162065-de5c2e25-fb42-4069-bf59-412f02306b4c.png">

Please help me check.
Thank you very much!

### To Reproduce

_No response_

### System

```shell
System:
  OS: macOS 12.6
  CPU: (10) arm64 Apple M1 Pro
Binaries:
  Node: 16.15.1 - ~/.nvm/versions/node/v16.15.1/bin/node
  Yarn: 1.22.19 - ~/.nvm/versions/node/v16.15.1/bin/yarn
  npm: 8.11.0 - ~/.nvm/versions/node/v16.15.1/bin/npm
Browsers:
  Chrome: 102.0.5005.61
  Safari: 15.6.1
npmPackages:
  @storybook/addon-a11y: ^6.5.10 => 6.5.12 
  @storybook/addon-actions: ^6.5.10 => 6.5.12 
  @storybook/addon-controls: ^6.5.10 => 6.5.12 
  @storybook/addon-viewport: ^6.5.10 => 6.5.12 
  @storybook/builder-webpack5: ^6.5.10 => 6.5.12 
  @storybook/manager-webpack5: ^6.5.10 => 6.5.12 
  @storybook/web-components: ^6.5.10 => 6.5.12
```


### Additional context

_No response_
Repository: godot
Issue: ScriptEditor: possible to have the same script open multiple times
Labels: bug,topic:editor

### Godot version

4.0 Beta3

### System information

Windows 10

### Issue description

It is possible to open the same script multiple times in the script editor. This results in a reappearing "The file on disk is newer"-warning until the duplicate scripts are closed. 

![Capture](https://user-images.githubusercontent.com/93336644/197147712-d9ad0403-d6f5-477b-95da-6ff8a3bb6038.JPG)
(identical file names except upper and lower case. Windows does not really separate between upper and lower case)

I think there needs to be a check earlier on if the file paths are identical (when converted to lower case). If only the case is different one option is to flat out ignore the rename (because of Windows and like Windows does). The - I imagine - safest other option would be to rename the path automatically first to an intermediate path, also to make sure that Windows renames folders correctly.

The following code in dir_access_windows.cpp seems relevant:
```
// If we're only changing file name case we need to do a little juggling
	if (p_path.to_lower() == p_new_path.to_lower()) {
		if (dir_exists(p_path)) {
			// The path is a dir; just rename   <== (me: there probably needs to happen some juggling here)
			return ::_wrename((LPCWSTR)(p_path.utf16().get_data()), (LPCWSTR)(p_new_path.utf16().get_data())) == 0 ? OK : FAILED;
		}
		// The path is a file; juggle
		WCHAR tmpfile[MAX_PATH];
```
I also think there needs to be an OS independent check earlier. IMHO it should not be possible on any OS to have file paths that differ only in case in order to enforce portability.




### Steps to reproduce

The first three steps have already been done in minimal reproduction project.
(
1. create "X/X.tscn" and "X/X.gd"
2. apply X.gd to the root of X.tscn and save
3. open the script
)

4. Rename the folder "X" to "x", this will result in an error but temporarily create the folder.
You should now have "x/X.gd" and "X/X.gd" open inside the script editor.

### Minimal reproduction project

[RenameBug.zip](https://github.com/godotengine/godot/files/9837717/RenameBug.zip)
Renaming the folder "X" to "x" should be enough to trigger the bug. This only seems to work the first time and is probably a Windows specific bug.
Repository: opencv
Issue: ret, frame = video.read()   add Back to  audio
Labels: feature

video= cv2.VideoCapture('rtmp://**')
while (video.isOpened()): 
    ret, frame= video.read()
    #frame  add check type  image and audio

### Descripe the feature and motivation

 add Back to  audio

### Additional context

 add Back to image and audio

 add Back to  audio

Add back images and audio, now not just pictures, but also sound. Hope to add this function, thank you very much!!

I can process images separately, merge sounds, and then use ffmpeg push stream. That's great.
Repository: neovim
Issue: Treesitter hangs neovim when trying to open a big log file with JSON lines
Labels: bug,performance,treesitter

### Neovim version (nvim -v)

NVIM v0.9.0-dev-143+ga288b4f21

### Vim (not Nvim) behaves the same?

no, VIM - Vi IMproved 9.0 (2022 Jun 28, скомпільовано Sep 01 2022 21:10:19)

### Operating system/version

Arch Linux

### Terminal name/version

qterminal 1.1.0

### $TERM environment variable

tmux-256color

### Installation

Any way (pacman, build)

### How to reproduce the issue

The issue only happens with TreeSitter enabled, doesn't with `nvim --clean`.

```
journalctl -o json > journal.json    # ~400 MB
nvim journal.json
```

### Expected behavior

The file is opened with TreeSitter disabled if it can't chew it, but neovim remains functional.

### Actual behavior

Neovim hangs hard, no way to stop it except of `kill -KILL`.
```
$ perf report
  49,37%  nvim     libtree-sitter.so.0.0   [.] ts_subtree_summarize_children                                                                                    
  23,77%  nvim     libtree-sitter.so.0.0   [.] ts_subtree_retain                                                                                                
  19,14%  nvim     libtree-sitter.so.0.0   [.] ts_subtree_release                                                                                               
   1,15%  nvim     libc.so.6               [.] 0x0000000000153b4a                                                                                               
```
Repository: pytorch
Issue: pytorch could not build from source with cudnn 8.0.5
Labels: module: build,module: cudnn,module: cuda,triaged

### 🐛 Describe the bug

pytorch could not build from source with cudnn 8.0.5, since cudnn-frontend in thirdparty will use `CUDNN_DATA_INT64` and other API such as `CUDNN_POINTWISE_RELU_BWD`, whereas CUDNN 8.0.5 API seems not to have (https://docs.nvidia.com/deeplearning/cudnn/archives/cudnn-805/api/index.html).
```
pytorch/cmake/../third_party/cudnn_frontend/include/cudnn_frontend_utils.h: In function 'std::__cxx11::string cudnn_frontend::to_string(cudnnDataType_t)':
pytorch/cmake/../third_party/cudnn_frontend/include/cudnn_frontend_utils.h:93:14: error: 'CUDNN_DATA_INT64' was not declared in this scope
         case CUDNN_DATA_INT64:
              ^~~~~~~~~~~~~~~~
pytorch/cmake/../third_party/cudnn_frontend/include/cudnn_frontend_utils.h:93:14: note: suggested alternative: 'CUDNN_DATA_INT8x4'
         case CUDNN_DATA_INT64:
              ^~~~~~~~~~~~~~~~
              CUDNN_DATA_INT8x4
pytorch/cmake/../third_party/cudnn_frontend/include/cudnn_frontend_utils.h:95:14: error: 'CUDNN_DATA_BFLOAT16' was not declared in this scope
         case CUDNN_DATA_BFLOAT16:
              ^~~~~~~~~~~~~~~~~~~
pytorch/cmake/../third_party/cudnn_frontend/include/cudnn_frontend_utils.h:95:14: note: suggested alternative: 'CUDNN_DATA_FLOAT'
         case CUDNN_DATA_BFLOAT16:
              ^~~~~~~~~~~~~~~~~~~
              CUDNN_DATA_FLOAT
```


### Versions

Pytorch 1.12.0

cc @malfet @seemethere @csarofeen @ptrblck @xwang233 @ngimel
Repository: stable-diffusion-webui
Issue: [Feature Request]: Batch queue IMG2IMG with random images pulled from folder.
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 ?

Hoping for an option that would allows for batch queueing of prompts for IMG2IMG that, when run, would pull a random image from a folder of images for each new prompt.  

I still use an colab a guy put together here (https://github.com/vincefav/stable-diffusion-lite) that does this.  At night,  I love being able to setup 100+ prompts, and a good folder of random images, so I'll have some cool stuff to look through in the morning and pick out the gems.




### Proposed workflow

1. Go to IMG2IMG
2. Select a folder with images
3. Either have a textbox that allows for listed prompts, or use the script option.
4. Execute the generating and images will be pulled randomly. General settings will be the same (cfg/steps/res), but the images used will be different.




### Additional information

Thanks for reading, and sorry if somehow I'm overlooking a way to do this in the current build(s). Asked about this first in discussion here yesterday: https://github.com/AUTOMATIC1111/stable-diffusion-webui/discussions/3243
Repository: material-ui
Issue: extendTheme utility included into final bundle, potential bundle size optimization
Labels: performance,package: joy-ui

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Just installing the latest `@mui/joy` into the project. Analysing  bundle size i noticed that extendTheme utility (~12kb size) is included into the production bundle. I am using default next.js with official `create-next-app`. 

I was wondering if this is necessary? My understanding is that `extendTheme` utility is used to merge default and custom theme but if no custom theme is used I do not see why it would be included.

### Current behavior 😯

extendTheme utility (~12kb size) is included with final bundle even though it is not imported anywhere. 

### Expected behavior 🤔

extendTheme utility (~12kb size) is NOT included with final bundle if it is not imported inside the project. If it is imported for custom theme support then it is of course logical that it is included.

### Context 🔦

Just trying to optimize bundle size because ~12kb is 15% of the whole size of `@mui/joy` that is imported into my project/case.

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: macOS 12.6
  Binaries:
    Node: 16.17.1 - ~/.volta/tools/image/node/16.17.1/bin/node
    Yarn: 1.22.18 - ~/.volta/tools/image/yarn/1.22.18/bin/yarn
    npm: 8.15.0 - ~/.volta/tools/image/node/16.17.1/bin/npm
  Browsers:
    Chrome: 106.0.5249.119
    Edge: Not Found
    Firefox: Not Found
    Safari: 16.0
  npmPackages:
    @emotion/react: ^11.10.4 => 11.10.4
    @emotion/styled: ^11.10.4 => 11.10.4
    @mui/base:  5.0.0-alpha.101
    @mui/core-downloads-tracker:  5.10.9
    @mui/icons-material: ^5.10.9 => 5.10.9
    @mui/joy: ^5.0.0-alpha.49 => 5.0.0-alpha.49
    @mui/material:  5.10.9
    @mui/private-theming:  5.10.9
    @mui/styled-engine:  5.10.8
    @mui/system:  5.10.9
    @mui/types:  7.2.0
    @mui/utils:  5.10.9
    @types/react: 18.0.21 => 18.0.21
    react: 18.2.0 => 18.2.0
    react-dom: 18.2.0 => 18.2.0
    typescript: 4.8.4 => 4.8.4
```
</details>
Repository: transformers
Issue: Add translation of docs to greek
Labels: WIP

I thought it would be awsome to add greek translation to the documentation I currently have translated only the index.mdx
Repository: godot
Issue: Crash when Loading Some Meshes
Labels: bug,topic:rendering,topic:import,crash,topic:3d

### Godot version

4.0 Beta 3

### System information

Windows 11, Vulkan, GTX 1050 Ti 516.94

### Issue description

Some Meshes Crash the Engine when attempting to put them on a mesh instance. Also they are clearly broken in the inspector preview.

### Steps to reproduce

Open MRP, Inspect OBJ, Try to assign it to a Mesh Instance

### Minimal reproduction project

[Crash.zip](https://github.com/godotengine/godot/files/9838614/Crash.zip)