sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Tests fail to run, if ~/.cache directory does not exist
Labels: bug,topic:tests

### Godot version

v4.0.alpha.custom_build [2c85f2a8f]

### System information

Debain 11

### Issue description

After building godot with tests enabled (`scons -j 6 platform=linuxbsd use_lto=yes target=release_debug tests=yes`), Tests can not be run, if there is no directory `~/.cache`.

```
./bin/godot.linuxbsd.opt.tools.64 --test
```
results in
```
godot-compile  | ERROR: Can't save PNG at path: '/home/godot/.cache/image.png'.
godot-compile  |    at: save_image (drivers/png/resource_saver_png.cpp:56)
godot-compile  | ERROR: Condition "!ref" is true. Returning: ERR_FILE_CANT_WRITE
godot-compile  |    at: save_exr (modules/tinyexr/image_saver_tinyexr.cpp:279)
godot-compile  | ERROR: Error opening file '/home/godot/.cache/image.png'.
godot-compile  |    at: load_image (core/io/image_loader.cpp:55)
godot-compile  | ERROR: Condition "len < 4" is true. Returning: ERR_INVALID_DATA
godot-compile  |    at: decode_variant (core/io/marshalls.cpp:101)
godot-compile  | ERROR: Condition "(type & 0xFF) >= Variant::VARIANT_MAX" is true. Returning: ERR_INVALID_DATA
godot-compile  |    at: decode_variant (core/io/marshalls.cpp:105)
godot-compile  | ERROR: Can't open file to write: /home/godot/.cache/output_empty.pck.
godot-compile  |    at: pck_start (core/io/pck_packer.cpp:92)
godot-compile  | ERROR: File must be opened before use.
godot-compile  |    at: flush (core/io/pck_packer.cpp:159)
[...]
```

I would expect that tests can be run, even if the directory `~/.cache` does not exist.

I noticed this behavior in the docker container, that I use for compiling godot.

Workaround: run `mkdir ~/.cache` before running the tests.

### Steps to reproduce

Within the source code repository root:
1. `scons -j 6 platform=linuxbsd use_lto=yes target=release_debug tests=yes`
2. `mv ~/.cache ~/.cache-tmp` (backup cache ... just in case)
3. `./bin/godot.linuxbsd.opt.tools.64 --test` (this command fails)
4. `mv ~/.cache-tmp ~/.cache` (restore cache)


### Minimal reproduction project

not applicable
Repository: pytorch
Issue: index_add : Inconsistent between CPU and CUDA
Labels: module: autograd,module: cuda,triaged

### 🐛 Describe the bug

```python
import torch
# device='cpu'  # Works

# RuntimeError: Source/destination tensor have different slice sizes (%ld vs %ld)123
device='cuda'

t=torch.zeros(4, 4, 3, device=device, requires_grad=True)
i=torch.tensor([0,1,2,3], device=device)
v=torch.tensor([[6.,7,8], [1,2,3], [6,7,8], [1,2,3]], device=device, requires_grad=True)

print(t.index_add(0,i,v))

```

Found while reproducing the issue (with `cuda`): https://github.com/pytorch/pytorch/issues/71155

### Versions

master

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7 @ngimel
Repository: flutter
Issue: [Flutter drive/integration_test] improve commands experience
Labels: c: new feature,platform-android,tool,framework,platform-web,c: proposal,f: integration_test,P3,team-framework,triaged-framework

Since the area of focus for 2022 roadmap is developer experience, the developer experience regarding integration test commands could be improved. Mainly by not requiring hard coded device ids. 

Currently you have to:

 - for web, start chromedriver with the correct port in another shell
 - for android, start the emulator and set the right emulator id in the command
 
Here is a few ideas, for android it could:

```
 1. check that `adb devices` has devices
 2a. if multiple devices are available display menu to pick device on which to run 
 3a. run
 
 2b. there is no device then display menu to pick emulator from `emulator -list-avds`
 3b. wait emulator started
 4b. run test on that emulator
 
 2c. if argument `--first-device` is passed, run test on first device found in `adb devices`, same for `--first-emulator`
```
 
 For web it could:
 
```
   1. start chromedriver
   2. run tests with the correct port
   3. kill both unless `--keep-chromedriver-alive`
```
   
   
The `--port` parameter is also lacking in web integration test, which makes whitelisting localhost:port impossible, you have to whitelist every ports.
Repository: youtube-dl
Issue: Don't download -f bestvideo to --extract-audio 
Labels: request

## Checklist

- [x] I'm reporting a feature request
- [x] I've verified that I'm running youtube-dl version **2021.12.17**
- [x] I've searched the bugtracker for similar feature requests including closed ones


## Description

I think that specifying `-x/--extract-audio` should make youtube-dl disregard video-specific format specifications.

I put `--format "bestvideo[height<=1080]+bestaudio/best[height<=?1080]"` in my config file because this is what I want when downloading videos. youtube-dl also follows this when I specify `-x` on the command line even though it is irrelevant and results in downloading a large video file that is not needed.

I think with `-x` the format should translate to `ø+bestaudio/best[audio]ø ==> bestaudio`.

As a workaround, I put  `alias yx="youtube-dl -x -f bestaudio"` in my `.zshrc`.
Repository: ant-design
Issue: Virtual scrollbar disappears after selecting items
Labels: help wanted,Inactive

- [ ] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### Reproduction link
[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/z5emb)

### Steps to reproduce
Opening the select -> select an item -> wait a second -> scrollbar disappears.

### What is expected?
Scrollbar should be visible.

### What is actually happening?
Scrollbar disappears.

| Environment | Info |
|---|---|
| antd | 4.18.5 |
| React | 16.18 |
| System | Windows, linux |
| Browser | Chrome 97.0.4692.71 |

---
We got an issue from a customer which doesn't have a scroll on his mouse. So he get stuck on our application. I understand the feature of disappearing the scrollbar, but at least when onMouseMove event is triggered it should be visible again.


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: pytorch
Issue: `svd_backward`: does not handle inputs of rank `r < min(m, n)`.
Labels: module: autograd,triaged,module: linear algebra


An oversight from our side is that while reviewing https://github.com/pytorch/pytorch/pull/70253 we forgot to consider the case of inputs or rank `< min(m, n)`. Since the branching logic is based solely on `m` and `n`, certain code paths will not be executed if, for example, `m = n` and all the inputs to `svd_backward` are matrices with `< min(m, n)` rows/columns.
This does not affect the user, as such inputs are never supplied to `svd_backward` from within the public API, but it might affect functions like https://github.com/pytorch/pytorch/pull/71126.


cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7 @jianyuh @mruberry @walterddr @IvanYashchuk @xwang233
Repository: neovim
Issue: Option for the `confirm` option to always confirm Neovim exit, regardless of buffer status
Labels: enhancement

### Feature already in Vim?

No

### Feature description

An option like `:set confirm` that will _always_ confirm that you want to exit Neovim, regardless of whether you have unsaved buffers or not. I've tried implementing something like this as a plugin but it doesn't really work.
Repository: pytorch
Issue: Batched sparse-sparse matrix multiplication/ sparse torch.einsum
Labels: module: sparse,feature,triaged

### 🚀 The feature, motivation and pitch

I want to do a sort of batched sparse-sparse matrix multiplication, but specifically in the scenario where I have two hybrid sparse coo tensors of the shape (N,N,C), where only the C dimension is a dense tensor. The behaviour I am looking for is that of a batched sparse-sparse matrix multiplication where the C dimension is in effect the batch dimension. Or equivalently expressed in torch.einsum: "i k d, j k d -> i j d" but only over the sparse indices in the first two dimensions.

If there exists a torch.sparse.bmm() function, it would be possible to permute the indices and do this I think.

### Alternatives

The only alternative I can come up with is to allow torch.einsum to work on sparse operands and only consider operating the einsum over the existing sparse indices in the tensor.

### Additional context

I need the feature to implement the TriangleMultiplication (Line 4 of Alg. 11 in the Supplementary Material) from Alphafold2 but for graphs batched as one large disconnected graph as is common in pytorch_geometric.

cc @nikitaved @pearu @cpuhrsch
Repository: godot
Issue: Cannot Read C# Script Class
Labels: bug,needs testing,topic:dotnet

### Godot version

3.4.2 Stable

### System information

Windows 11, GLES3

### Issue description

My Project is using dotnet 5 C# last major

![image](https://user-images.githubusercontent.com/75127571/151835695-918dc98c-4646-42b4-a1c6-39f4ce5f9396.png)
I was write correct class (It can run in the pass

![image](https://user-images.githubusercontent.com/75127571/151835861-10b3c33e-4499-4a21-8cc3-10a333fc54ee.png)
But it cannot read class

### Steps to reproduce

None

### Minimal reproduction project

_No response_
Repository: create-react-app
Issue: `react-scripts build` fails with Module not found: Error: Can't resolve '../../helpers/esm/typeof'
Labels: needs triage,issue: bug report

### Describe the bug

After upgrading `react-scripts` to latest `5.0.0` (was: `4.0.1`) I cannot build my project because I get this:

```
Module not found: Error: Can't resolve '../../helpers/esm/typeof' in '/Users/ickata/Work/Galaxy/node_modules/@babel/runtime/helpers/esm'
Did you mean 'typeof.js'?
BREAKING CHANGE: The request '../../helpers/esm/typeof' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
```

### Did you try recovering your dependencies?

Yes, no success.

### Which terms did you search for in User Guide?

 - "Module not loaded"
 - "react-scripts build"

### Environment

 - MacOS Monterey (12.1)
 - NodeJS v14.17.5

```
Environment Info:

  current version of create-react-app: 5.0.0
  running from /Users/ickata/.npm/_npx/39396/lib/node_modules/create-react-app

  System:
    OS: macOS 12.1
    CPU: (8) x64 Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz
  Binaries:
    Node: 14.17.5 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 6.14.14 - /usr/local/bin/npm
  Browsers:
    Chrome: 97.0.4692.99
    Edge: 87.0.664.75
    Firefox: 96.0.2
    Safari: 15.2
  npmPackages:
    react: ^17.0.1 => 17.0.1
    react-dom: ^17.0.1 => 17.0.1
    react-scripts: ^5.0.0 => 5.0.0
  npmGlobalPackages:
    create-react-app: Not Found
```

### Steps to reproduce

No exact steps, however I am not able to reproduce the issue w/ a fresh CRA install.
Repository: PowerToys
Issue: [Fluent UX] Keyboard Manager
Labels: Product-Keyboard Shortcut Manager,Area-User Interface,External Dependency-WinUI 3,UI refresh

### Provide a description of requested docs changes

### Description of the new feature / enhancement

Windows 11 introduces a new direction of Fluent Design - it would be great if all PowerToys features would look and feel native to the OS. WinUI 3 should make this an easy transition. Some things that come to mind:

**General**
- [ ] Combining the remap key and shortcut into a single experience, making it a true "Keyboard Manager".
- [ ] Ability to (temporarily) turn on / off certain remappings.
- [ ] Adopting WinUI 3 (and it's default styling for Windows 11)
- [ ] Resolve common accessibility issues by adopting standard UI elements and colors
- [ ] Modern input (touch / pen)

Issues we can address with this UI redesign: #15340, #15340, #13382, #10552, #10042, #8798, #8793, #7304, #7070, #7054, #7054, #7054, #2170

### Mock-up
![KBMvNext](https://github.com/microsoft/PowerToys/assets/9866362/de0f00c7-34c4-478a-a254-08eb59bc481b)



WinUI 2.6 (UWP) source code: https://github.com/niels9001/KBMUX

Let's use this issue to track UI related concerns, feature requests and other feedback!
Repository: node
Issue: Error when restarting a `node inspect` run after setting break point twice
Labels: debugger

```zsh
❯ node -v
v15.2.0
❯ npm -v
7.0.8
❯ cat test.js
process.stdin.resume();
❯ ./node_modules/node-inspect/cli.js test.js
< Debugger listening on ws://127.0.0.1:9229/da6a93a7-27a4-4eb0-9abd-da7bf4d7e812
< For help, see: https://nodejs.org/en/docs/inspector
< Debugger attached.
Break on start in test.js:1
> 1 process.stdin.resume();
  2 
debug> setBreakpoint(1)
> 1 process.stdin.resume();
  2 
debug> restart
< Debugger listening on ws://127.0.0.1:9229/bd969e56-b38e-4c0e-a202-e99cbc34dbd2
< For help, see: https://nodejs.org/en/docs/inspector
< Debugger attached.
Warning: script 'file:///home/raisinten/Desktop/universe/temp/project/report/report2/test.js' was not loaded yet.
1 breakpoints restored.
Break on start in test.js:1
> 1 process.stdin.resume();
  2 
debug> setBreakpoint(1)
> 1 process.stdin.resume();
  2 
debug> restart
< Debugger listening on ws://127.0.0.1:9229/3f518903-5194-437a-ac6d-5f68e9186f6e
< For help, see: https://nodejs.org/en/docs/inspector
< Debugger attached.
Warning: script 'file:///home/raisinten/Desktop/universe/temp/project/report/report2/test.js' was not loaded yet.
There was an internal error in node-inspect. Please report this bug.
Breakpoint at specified location already exists. - undefined
Error: Breakpoint at specified location already exists. - undefined
    at _pending.<computed> (/home/raisinten/Desktop/universe/temp/project/report/report2/node_modules/node-inspect/lib/internal/inspect_client.js:243:27)
    at Client._handleChunk (/home/raisinten/Desktop/universe/temp/project/report/report2/node_modules/node-inspect/lib/internal/inspect_client.js:213:11)
    at Socket.emit (node:events:329:20)
    at Socket.EventEmitter.emit (node:domain:529:15)
    at addChunk (node:internal/streams/readable:304:12)
    at readableAddChunk (node:internal/streams/readable:279:9)
    at Socket.Readable.push (node:internal/streams/readable:218:10)
    at TCP.onStreamRead (node:internal/stream_base_commons:192:23)
    at TCP.callbackTrampoline (node:internal/async_hooks:129:14)
```
I would expect it to not crash and work like the first iteration of `setBreakpoint + restart`.
Repository: material-ui
Issue: [link] What's the recommended way of using MUI Link with Next.js Link?
Labels: docs,component: link,nextjs

### Current behavior 😯

Currently the way its suggested to integrate MUI Link to NextJS Link component is use the example in 
https://github.com/mui-org/material-ui/blob/ec5df5f94f472628103eb1cfbecccc6afc2658bd/examples/nextjs-with-typescript/src/Link.tsx

### Expected behavior 🤔

https://stackoverflow.com/a/66228870
This basically, gives the same functionality, without the overhead.

```
import NextLink from 'next/link'
import MuiLink from '@material-ui/core';

<NextLink href="/" passHref>
    <MuiLink>MyLink</MuiLink>
</NextLink>
```

### Steps to reproduce 🕹

https://stackoverflow.com/a/66228870 
vs
https://github.com/mui-org/material-ui/blob/ec5df5f94f472628103eb1cfbecccc6afc2658bd/examples/nextjs-with-typescript/src/Link.tsx 


### Context 🔦

What's the recommended way of using Mui Link with NextJs Link.

### Your environment 🌎

<details>
  <summary>`npx @mui/envinfo`</summary>
 ..
```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>
Repository: node
Issue: Syntax error not showing in stderr with `node --inspect-brk` in node 12+
Labels: inspector

HI,
I'm trying a simple script with a syntax error in it but I'm not getting the error displayed when running with node versions 12+. Older versions are ok. I've tried this script (in test.js):

```
console.log(1)
console.log(2
console.log(3)
```

When running with node 11, I'm seeing the error:

```
# node-inspect test.js
< Debugger listening on ws://127.0.0.1:9229/9f22bef2-a0db-4c2d-89d6-f741e1f3c9cd
< For help, see: https://nodejs.org/en/docs/inspector
< Debugger attached.
< /test.js:2
< console.log(1
<             ^
< SyntaxError: missing ) after argument list
<     at Module._compile (internal/modules/cjs/loader.js:760:23)
<     at Object.Module._extensions..js (internal/modules/cjs/loader.js:827:10)
<     at Module.load (internal/modules/cjs/loader.js:685:32)
<     at Function.Module._load (internal/modules/cjs/loader.js:620:12)
<     at Function.Module.runMain (internal/modules/cjs/loader.js:877:12)
<     at internal/main/run_main_module.js:21:11
< Waiting for the debugger to disconnect...
debug>
```

But with node 12+ (tried 13,14) the error is not echoed in the terminal and I'm getting:

```
/ # node-inspect test.js
< Debugger listening on ws://127.0.0.1:9229/583b30fe-ab2d-43f9-af41-a23d0148c985
< For help, see: https://nodejs.org/en/docs/inspector
< Debugger attached.
< Waiting for the debugger to disconnect...
debug>
```

I would like to get the error echoed in the terminal. Is this a valid output or I'm doing anything wrong?
Thanks-
Repository: node
Issue: node inspect crashes when tab-completing with a require
Labels: repl,debugger

<!--
Thank you for reporting a possible bug in Node.js.

Please fill in as much of the template below as you can.

Version: output of `node -v`
Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)
Subsystem: if known, please specify the affected core module name

If possible, please provide code that demonstrates the problem, keeping it as
simple and free of external dependencies as you can.
-->

* **Version**: v11.1.0
* **Platform**: Linux setp 4.19.1-arch1-1-ARCH nodejs/node-inspect#1 SMP PREEMPT Sun Nov 4 16:49:26 UTC 2018 x86_64 GNU/Linux
* **Subsystem**:

<!-- Please provide more details below this comment. -->
Steps to reproduce:

0. Create an empty file named "test.js"
1. Run `node inspect test.js`
2. Enter the debug repl
3. Type `require("`
4. Press tab

Result: Node prints the following message to standard error, then exits with status 1.
```
There was an internal error in node-inspect. Please report this bug.
Cannot read property 'extensions' of undefined
TypeError: Cannot read property 'extensions' of undefined
    at REPLServer.complete (repl.js:1031:51)
    at REPLServer.completer (repl.js:492:14)
    at REPLServer.Interface._tabComplete (readline.js:476:8)
    at REPLServer.Interface._ttyWrite (readline.js:975:16)
    at REPLServer.self._ttyWrite (repl.js:719:7)
    at ReadStream.onkeypress (readline.js:178:10)
    at ReadStream.emit (events.js:182:13)
    at ReadStream.EventEmitter.emit (domain.js:441:20)
    at emitKeys (internal/readline.js:424:14)
    at emitKeys.next (<anonymous>)
```

Observed rules for reproduction:

* test.js can be any JavaScript file.
* A single quote may be substituted for the double quote in step 3.
* `require("` may be preceded by any JavaScript code.
* Space characters may be typed between `require` and `("`.
* The paren must be immediately followed by the quote (no whitespace).
* Any additional characters may be typed before pressing tab.
* The cursor must be somewhere after the quote when pressing tab.
Repository: flutter
Issue: [camera] Support focus, zoom, exposure and flash controls on windows platform
Labels: c: new feature,platform-windows,p: camera,package,a: desktop,P3,team-windows,triaged-windows

## Use case

[#4641](https://github.com/flutter/plugins/pull/4641) adds support for camera on Windows platform but is missing implementation for 

- **Focus**: changing focus mode between auto and manual
- **Zoom**: fetching zoom range and setting zoom value
- **Exposure**: changing exposure mode, fetching exposure range and setting exposure value
- **Flash**: changing flash mode

## Proposal

On Windows platform, some [constraints and settings](https://docs.microsoft.com/en-us/windows/win32/api/strmif/ne-strmif-cameracontrolproperty) are controlled with [IAMCameraControl](https://docs.microsoft.com/en-us/windows/win32/api/strmif/nn-strmif-iamcameracontrol) interfaces including:
  - Zoom,
  - Exposure
  - Focus
  
[IMFExtendedCameraControl](https://docs.microsoft.com/en-us/windows/win32/api/mfidl/nn-mfidl-imfextendedcameracontrol) can be used to control following settings:
  - [Flash mode](https://docs.microsoft.com/en-us/windows-hardware/drivers/stream/ksproperty-cameracontrol-flash-property) 
  - [Extended focus settings](https://docs.microsoft.com/en-us/windows-hardware/drivers/stream/standardized-extended-controls-#advanced-focus)
Repository: rust
Issue: Adding an unreachable branch helps optimize the code when matching on `x % N`
Labels: A-LLVM,I-slow,C-enhancement,A-codegen,E-needs-test,T-compiler,C-optimization

Consider this example:
```rust
pub fn parse(x: usize) -> usize {
    match x % 5 {
        0 => f1(x),
        1 => f2(x),
        2 => f3(x),
        3 => f4(x),
        4 => f5(x),
        // 5 | 6 | 7 => loop{},
        _ => loop{},
    }
}
```
It currently generates similar LLVM-IR:
```llvm
start:
  %_2 = urem i64 %x, 5, !dbg !10
  switch i64 %_2, label %bb12 [
    i64 0, label %bb2
    i64 1, label %bb4
    i64 2, label %bb6
    i64 3, label %bb8
    i64 4, label %bb10
  ], !dbg !11
; ...
bb12:
  br label %bb12, !dbg !32
```
Even though the default branch is unreachable (`x % 5` can't be greater than 4) it is still generated.

But, when un-commenting `5 | 6 | 7 => loop{}` line (still unreachable branch, that does the same as default) the default branch becomes `unreachable`:
```llvm
start:
  %_2 = urem i64 %x, 5, !dbg !10
  switch i64 %_2, label %bb14 [
    i64 0, label %bb2
    i64 1, label %bb4
    i64 2, label %bb6
    i64 3, label %bb8
    i64 4, label %bb10
  ], !dbg !11
; ...
bb14:
  unreachable
```

So, adding an **unreachable** branch that does **the same as the default** helps optimize the code.

Some notes:
- These differences then propagate to assembler, i.e. it also has an unreachable branch when `5 | 6 | 7` is commented-out
- [godbolt link](https://godbolt.org/z/o6hPW16MW)
- Range patterns (like `5..=7`) do **not** help
- Making the default branch `5 | 6 | 7 | _` doesn't help either
- Similar things happen for any `N` in `x % N` that is not a power of two -- adding unreachable branches until the last branch has a power-of-two-minus-one-value helps optimizing the code
  - [`N = 3`](https://godbolt.org/z/5ezr3PP51) (`3 =>`)
  - [`N = 9`](https://godbolt.org/z/o8rdcaK95) (`9 | 10 | 11 | 12 | 13 | 14 | 15 =>`)
  - [`N = 14`](https://godbolt.org/z/76xexbr4M) (`14 | 15 =>`)
- `loop{}`s can be replaced with anything else, for example `unreachable!()` or `panic!()`, effect is still the same
  - in case of panic-like things not removing the panicking branch seems like a big deal
  - I've used `loop{}`s to make diffs less noisy
- `if-else-if` chains are identical to `match` here
- clang seems to handle this situation just fine in any case: [godbolt link](https://godbolt.org/z/xf47WYE8q)
  - it also makes the last reachable branch default in `llvm-ir`, instead of generating an `unreachable` one