sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: terminal
Issue: Disable scroll keyboard shortcut when in alternate screen mode
Labels: Area-TerminalControl,Product-Terminal,Issue-Task

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement

By default ctrl+shift+up/down scrolls windows terminal up or down. This is good for normal terminal usage, however it is not generally useful when in an alternate screen app like vim, emacs, tmux, etc. which generally handle scrolling internally. These apps also can have ctrl+shift+up/down bound to useful shortcuts, like in emacs by default it will extend the selection up or down by a paragraph.
I would suggest if possible an option to disable the scrolling shortcut when in alternate screen mode and pass it through to the underlying program.
Repository: godot
Issue: System.TypeInitializationException Causes Editor To Crash
Labels: bug,topic:editor,confirmed,topic:dotnet

**Godot version:**
Godot Engine v3.2.3.stable.mono.official -- Open GL 3.0 Renderer: GeForce RTX 3070/PCIe/SSE2
Microsoft Visual Studio Community 2019 Version 16.8.4

**OS/device including version:**
Windows 10 (19042.746)

**Issue description:**
Building project, either through 'Build' at top right of Godot, or building the solution in Visual Studio causes Godot to crash. The application and visual studio (if either are running) don't crash, just the editor.

From some more testing, it seems like it only crashes if Visual Studio is open, or has been opened since the editor was started.

I've attached the console log. The last `System.TypeInitializationException` shows up just before the editor crashes, and the one before that shows up when I open the editor.
![image](https://user-images.githubusercontent.com/28535385/107002493-4e504100-67c6-11eb-9984-674884448f3f.png)

**Steps to reproduce:**
My project didn't used to do this and other projects don't cause this issue, so I'm not sure how to reproduce this.

**Minimal reproduction project:**
Couldn't reproduce
Repository: pytorch
Issue: BatchNorm3d error : CUDNN_STATUS_NOT_SUPPORTED
Labels: module: cudnn,triaged

## 🐛 Bug

`BatchNorm3d` raises an error related to `cudnn`. 
```
RuntimeError: cuDNN error: CUDNN_STATUS_NOT_SUPPORTED. This error may appear if you passed in a non-contiguous input.
```

Thanks for the help or any advice to solve this !!

## To Reproduce

```
import torch
torch.backends.cuda.matmul.allow_tf32 = True
torch.backends.cudnn.benchmark = True
torch.backends.cudnn.deterministic = False
torch.backends.cudnn.allow_tf32 = True
data = torch.rand(70, 32, 100, 100, 100, dtype=torch.float16, device='cuda', requires_grad=False)
net = torch.nn.BatchNorm3d(32).to('cuda')
out = net(data)
print(out.shape)
```

## Expected behavior

The code above should print
```
torch.Size([70, 32, 100, 100, 100])
```

## Environment

```
PyTorch version: 1.7.1
Is debug build: False
CUDA used to build PyTorch: 10.2
ROCM used to build PyTorch: N/A

OS: CentOS Linux release 7.9.2009 (Core) (x86_64)
GCC version: (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)
Clang version: Could not collect
CMake version: Could not collect

Python version: 3.9 (64-bit runtime)
Is CUDA available: True
CUDA runtime version: Could not collect
GPU models and configuration: 
GPU 0: Tesla V100-PCIE-16GB
GPU 1: Tesla V100-PCIE-16GB

Nvidia driver version: 440.33.01
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip3] numpy==1.19.5
[pip3] pytorch-ignite==0.5.0
[pip3] torch==1.7.1
[pip3] torchsummary==1.5.1
[pip3] torchvision==0.8.2
[conda] numpy                     1.19.5                   pypi_0    pypi
[conda] pytorch-ignite            0.5.0                    pypi_0    pypi
[conda] torch                     1.7.1                    pypi_0    pypi
[conda] torchsummary              1.5.1                    pypi_0    pypi
[conda] torchvision               0.8.2                    pypi_0    pypi
```


cc @csarofeen @ptrblck @xwang233
Repository: go
Issue: cmd/go: 'go mod vendor' should not remove existing non-Go content from the vendor subdirectory
Labels: NeedsInvestigation,modules

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

**Tl;dr**: Go is not the only tool I use in my project; I expect it share `vendor` peacefully.

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.15.8 linux/amd64
</pre>

(latest at the time of this writing)


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/raphael/.cache/go-build"
GOENV="/home/raphael/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/raphael/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/raphael/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/raphael/Code/tools/container-do/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build500284300=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

```Gemfile
# Gemfile
source "https://rubygems.org"

group :test do
  gem 'cucumber', '~> 5'
  gem 'rspec', '~> 3'
end
```

```
# go.mod
module github.com/reitzig/container-do

go 1.15

require (
	github.com/pelletier/go-toml v1.8.1
	go.uber.org/zap v1.16.0
)
```

```bash
bundle2.7 config set --local path 'vendor/bundle'
bundle2.7 install
go mod vendor
```

### What did you expect to see?

Ruby gems _and_ Go modules "installed" in `vendor`.

### What did you see instead?

Only Go modules in `vendor`.

### Workaround

Bundler leaves Go modules alone, so re-running `bundle install` after `go mod vendor` creates the desired state.
Repository: flutter
Issue: Paragraph.getWordBoundary doesn't return empty TextRange when offset out of bounds
Labels: a: tests,framework,engine,a: typography,has reproducible steps,P2,found in release: 3.3,found in release: 3.6,team-engine,triaged-engine

If you supply an out-of-range offset to `Paragraph.getLineBoundary`, then the result is `TextRange.empty` as expected. This is demonstrated with the following test:

```
test('Line boundary for out-of-range offset returns empty range', () {
  const text = 'Hello world';
  const offset = 1000;
  final paragraphStyle = ParagraphStyle(
    textDirection: TextDirection.ltr,
  );
  final paragraphBuilder = ParagraphBuilder(paragraphStyle)
    ..addText(text);
  final constraints = ParagraphConstraints(width: 300);
  final paragraph = paragraphBuilder.build();
  paragraph.layout(constraints);
  final range = paragraph.getLineBoundary(TextPosition(offset: offset));
  expect(range, TextRange.empty);
});
```

However if you do the same thing with `Paragraph.getWordBoundary`, the test fails. It returns a range from the end of the text to the offset. This isn't the behavior I expect, but is this intentional? 

Here is a test to demonstrate it:

```
test('word boundary for out-of-range offset returns empty range', () {
  const text = 'Hello world';
  const offset = 1000;
  final paragraphStyle = ParagraphStyle(
    textDirection: TextDirection.ltr,
  );
  final paragraphBuilder = ParagraphBuilder(paragraphStyle)
    ..addText(text);
  final constraints = ParagraphConstraints(width: 300);
  final paragraph = paragraphBuilder.build();
  paragraph.layout(constraints);
  final range = paragraph.getWordBoundary(TextPosition(offset: offset));
  expect(range, TextRange.empty);
});
```

This test fails:

```
Expected: TextRange:<TextRange(start: -1, end: -1)>
  Actual: TextRange:<TextRange(start: 11, end: 1000)>
```

Here is the relevant part of `flutter doctor -v`:

```
[✓] Flutter (Channel beta, 1.25.0-8.3.pre, on Mac OS X 10.15.4 19E266 darwin-x64, locale en)
    • Flutter version 1.25.0-8.3.pre at /Users/suragch/fvm/versions/beta
    • Framework revision 5d36f2e7f5 (3 weeks ago), 2021-01-14 15:57:49 -0800
    • Engine revision 7a8f8ca02c
    • Dart version 2.12.0 (build 2.12.0-133.7.beta)
```
Repository: flutter
Issue: [integration_test] - Support tags in integration test package
Labels: a: tests,c: new feature,c: proposal,f: integration_test,P3,team-framework,triaged-framework

## Use case
This is about new [integration_test](https://pub.dev/packages/integration_test) package

1. As an automation tester, I want to put tags on my e2e tests.
2. When running tests from the console I want to specify using those tags what tests to run.

For example:
_flutter drive --driver=test_driver/integration_test_driver.dart --target=test_driver/integration_test/filters_test.dart **--tags=smoke**_


ps. _I was searching for this capability or raised issue/task on your GitHub. But can't find it. If duplicate please remove or link it._
Repository: PowerToys
Issue: NumPad Keys that are not numbers missing from Keyboard Manager
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Needs-Team-Response

## ℹ Computer information

- PowerToys version: v0.31.1
- PowerToy Utility: Keyboard Manager
- Running PowerToys as Admin: No
- Windows build number: 20231.1000

### ✔️ Expected result

I expect to be able to remap other NumPad Keys

### ❌ Actual result

NumPad Keys except numbers and "Lock" are missing.

## 📷 Screenshots

![image](https://user-images.githubusercontent.com/13102251/107023643-33ba9f80-67a7-11eb-8457-f371bf142884.png)

![image](https://user-images.githubusercontent.com/13102251/107023664-3c12da80-67a7-11eb-89ae-8dbfb38d4391.png)
Repository: pytorch
Issue: Analytical metric package
Labels: module: distributions,feature,triaged,module: data

## 🚀 Feature
A set of functions that calculate metrics of various distributions
## Motivation

<!-- Please outline the motivation for the proposal. Is your feature request related to a problem? e.g., I'm always frustrated when [...]. If this is related to another GitHub issue, please link here too -->
I needed during my work many times to calcualte metrics such as KL of Gamma dist or Dirichlet or analytical form of Gaussians 
I believe that such can be benficial
## Pitch
You can find everything in this branch 
<!-- A clear and concise description of what you want to happen. -->

https://github.com/natank1/Closed-form-of-Various-Metircs

## Alternatives
Don know any
<!-- A clear and concise description of any alternative solutions or features you've considered, if any. -->

## Additional context

<!-- Add any other context or screenshots about the feature request here. -->


cc @VitalyFedyunin @ejguan @fritzo @neerajprad @alicanb @vishwakftw @nikitaved
Repository: godot
Issue: Editor text input cursor position resets on save
Labels: bug,topic:editor,confirmed

**Godot version:**
3.2.4-rc1
nb. I have noticed this behaviour in 3.2.3 too.

**OS/device including version:**
Ubuntu Linux 20.04

**Issue description:**
This only applies when editing nodes which have scripts attached to them.

When editing a value in the node inspector and the scene is saved (either automatically or pressing Ctrl+S), the cursor moves to the beginning of the line. This may be while I'm in the middle of typing, in which case, it feels pretty jarring.

This is possibly related to #20708.

**Steps to reproduce:**
* Attach a script to a node
* Edit eg. the node's 'editor description' in the inspector
* Press Ctrl+S
* Notice the cursor snap to home

**Minimal reproduction project:**
n/a
Repository: opencv
Issue: Improve all flann documentation
Labels: category: documentation,category: flann

##### System information (version)
- OpenCV => 4.5.1
- Operating System / Platform => N/A
- Compiler => N/A

##### Detailed description
If a user wanted to configure `cv::FlannBasedMatcher` to anything but the defaults they would have quite the struggle, even when looking directly at the source code. The documentation is sorely lacking, specifically for how to configure for use with binary descriptors. This is also true for `cv::flann::hierarchicalClustering()`.

##### Steps to reproduce

Visit the [docs](https://docs.opencv.org/4.5.1) and search for IndexParams

##### Issue submission checklist

 - [x] I report the issue, it's not a question
   <!--
   OpenCV team works with forum.opencv.org, Stack Overflow and other communities
   to discuss problems. Tickets with question without real issue statement will be
   closed.
   -->
 - [x] I checked the problem with documentation, FAQ, open issues,
       forum.opencv.org, Stack Overflow, etc and have not found solution
   <!--
   Places to check:
   * OpenCV documentation: https://docs.opencv.org
   * FAQ page: https://github.com/opencv/opencv/wiki/FAQ
   * OpenCV forum: https://forum.opencv.org
   * OpenCV issue tracker: https://github.com/opencv/opencv/issues?q=is%3Aissue
   * Stack Overflow branch: https://stackoverflow.com/questions/tagged/opencv
   -->
 - [x] I updated to latest OpenCV version and the issue is still there
   <!--
   master branch for OpenCV 4.x and 3.4 branch for OpenCV 3.x releases.
   OpenCV team supports only latest release for each branch.
   The ticket is closed, if the problem is not reproduced with modern version.
   -->
 - [x] There is reproducer code and related data files: videos, images, onnx, etc
   <!--
   The best reproducer -- test case for OpenCV that we can add to the library.
   Recommendations for media files and binary files:
   * Try to reproduce the issue with images and videos in opencv_extra repository
     to reduce attachment size
   * Use PNG for images, if you report some CV related bug, but not image reader
     issue
   * Attach the image as archive to the ticket, if you report some reader issue.
     Image hosting services compress images and it breaks the repro code.
   * Provide ONNX file for some public model or ONNX file with with random weights,
     if you report ONNX parsing or handling issue. Architecture details diagram
     from netron tool can be very useful too. See https://lutzroeder.github.io/netron/
   -->
Repository: flutter
Issue: [integration_test] - Support parametrized tests in integration test package
Labels: a: tests,c: new feature,framework,c: proposal,f: integration_test,P3,team-framework,triaged-framework

## Use case
Run the same test over and over again using different values.

1. As an automation tester, I want to make my e2e tests cleaner
2. I want to create one test and run it against few test data sets
3. I don't want to repeat the test with the same test steps few times for different data sets.

It's called parametrized tests or data-driven testing. 
It will be nice to have this feature, considering the DRY rule.

Example in JUnit [HERE](https://www.tutorialspoint.com/junit/junit_parameterized_test.htm)
Repository: rust
Issue: Apple Silicon M1 - libLLVMX86Disassembler.a: file too small to be an archive
Labels: O-macos,T-bootstrap,O-AArch64

On a `Mac mini (M1, 2020)` with macOS Big Sur `11.2 (20D64)`

running a `./x.py build` and letting it compile llvm from scratch results in:
```
error: failed to add native library /Users/walther/git/rust/build/aarch64-apple-darwin/llvm/build/lib/libLLVMX86Disassembler.a: file too small to be an archive

error: aborting due to previous error

error: could not compile `rustc_llvm`

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed
command did not execute successfully: "/Users/walther/git/rust/build/aarch64-apple-darwin/stage0/bin/cargo" "build" "--target" "aarch64-apple-darwin" "-Zbinary-dep-depinfo" "-j" "8" "--release" "--features" " llvm max_level_info" "--manifest-path" "/Users/walther/git/rust/compiler/rustc/Cargo.toml" "--message-format" "json-render-diagnostics"
expected success, got: exit code: 101
failed to run: /Users/walther/git/rust/build/bootstrap/debug/bootstrap build
```

Note, that `llvm` compilation itself seemed to complete successfully before it:

```
...
-- Installing: /Users/walther/git/rust/build/aarch64-apple-darwin/llvm/lib/cmake/llvm/./CheckLinkerFlag.cmake
cargo:root=/Users/walther/git/rust/build/aarch64-apple-darwin/llvm
        finished in 1726.572 seconds
Building stage0 compiler artifacts (aarch64-apple-darwin -> aarch64-apple-darwin)
...
```

The file in question seems to be `3.2M` in size. I do not know if that is indeed too small to be correct, or if there is some unknown error in detecting it.

```
ls -halF /Users/walther/git/rust/build/aarch64-apple-darwin/llvm/build/lib/libLLVMX86Disassembler.a
-rw-r--r--  1 walther  staff   3.2M Feb  5 16:02 /Users/walther/git/rust/build/aarch64-apple-darwin/llvm/build/lib/libLLVMX86Disassembler.a
```

This was ran at `rust` repository commit hash `9e5d58fb420a487ae30f38141eccdc8d79fb8d58`.

Note, I did not attempt to do any cross-compilation - this was simply cloning the repository and running `./x.py build`, with the expectation to build against the native `aarch64` target.
Repository: rust
Issue: replace usages of 'wc' in test scripts with simpler ways
Labels: C-cleanup,A-testsuite

https://github.com/rust-lang/rust/blob/730d6dfdddc0f55d9cbeedb29a14b342f74e2a9d/src/test/run-make-fulldeps/target-cpu-native/Makefile#L11
see also: https://github.com/rust-lang/rust/pull/53642#discussion_r212694002
As noted above, the snip `[ $(wc -c file | cut -d' ' -f1) == 0 ]` should be replaced with `! [ -s file ]` which should make such scripts more portable.
other locations of this are easily found with: https://github.com/rust-lang/rust/search?q=wc (only the `= "0"` or `-eq 0` or such usages are interesting)
Repository: excalidraw
Issue: wrap toolbar on small screens
Labels: mobile

either wrap:

![image](https://user-images.githubusercontent.com/5153846/107050223-447d0c80-67cb-11eb-83ad-88739ac0a66b.png)

or make the icons smaller?

Also we could possibly make the toolbar horizontally scrollable...
Repository: pytorch
Issue: [discussion] [python] Generic way for generating module-wrappers for stateless parametrized functions
Labels: feature,module: nn,triaged,better-engineering

A lot of functionality like activations is implemented as stateless functions with some scalar parameters. Corresponding modules usually just hold some of these parameters and pass them to the function during forward. This requires to write boiler-plate code for these modules.

An alternative way could be generic standard wrapper generator (at least for python) like `modularize` function below. Then PyTorch could have `nn.Hardtanh = modularize(F.hardtanh)`. Even if PyTorch can do it via codegen, such an utility would be useful for end users to avoid boiler-plate.

Typing information could also be generated dynamically from the corresponding typing signatures from inner functions.

```python
import torch

class Modularize(torch.nn.Module):
    def __init__(self, func, **kwargs):
        super().__init__()
        self.__name__ = func.__name__
        self.forward = lambda *a, **kw: func(*a, **kw, **kwargs)

def modularize(func, __name__ = None):
    return type(__name__ or 'Modularize_' + func.__name__, (torch.nn.Module, ), dict(__init__ = lambda self, **kwargs: torch.nn.Module.__init__(self) or setattr(self, 'kwargs', kwargs), forward = lambda self, *a, **kw: func(*a, **dict(self.kwargs, **kw))))

if __name__ == '__main__':
    def add(x, y):
        return x + y

    adder1_instance = Modularize(add, y = 1)
    adder_module = modularize(add)
    adder2_instance = adder_module(y = 2)

    x = torch.zeros(4)
    print(type(adder1_instance), adder1_instance(x))
    print(type(adder2_instance), adder2_instance(x))
```

cc @albanD @mruberry @jbschlosser @walterddr @kshitij12345 @saketh-are
Repository: flutter
Issue: Missing documentation for default textthemes
Labels: framework,f: material design,d: api docs,team-design,triaged-design

I was just confused that the default headline4 and headline5 had different colors. So I looked at the texttheme documentation: https://api.flutter.dev/flutter/material/TextTheme-class.html and the material design documentation: https://material.io/design/typography/the-type-system.html#type-scale and found nothing that would suggest this. I'd expected this to have been mentioned in the tables in the texttheme doc that list data about the default textthemes
Repository: TypeScript
Issue: Can't use async arrow function in/before super call
Labels: Bug,Rescheduled

# Bug Report

### 🔎 Search Terms

super async arrow function this

### 🕗 Version & Regression Information

This only occurs using a target version of ES2016 or lower.

### ⏯ Playground Link

https://www.typescriptlang.org/play?target=3&ts=4.1.3#code/MYGwhgzhAECC0G8BQ1rAPYDsIBcBOArsDungBQBmmAXNGQJTQC8AfNAAp7oC2AlhAFMAPADd0vACYtGyVKioMA3CmgBfJOqShIMAELQBADxwDMEmPFlosuQsVINEK1BAIAHAeUgBPTMDqMrE5ychjY6CACAHQg6ADmZABEABICILGJ9Mohqlkq6pqYAgDu0LpKQA

### 💻 Code

This works:
```ts
class A {
  constructor(fn: () => Promise<void>) {
    fn();
  }
}

class B extends A {
  constructor() {
    super(async function () {
      console.log("Hello");
    });
  }
}

new B();
```

This doesn't:
```ts
class A {
  constructor(fn: () => Promise<void>) {
    fn();
  }
}

class B extends A {
  constructor() {
    super(async () => {
      console.log("Hello");
    });
  }
}

new B();
```

The difference between the examples is the use of an arrow function vs a traditional function.

### 🙁 Actual behavior

It compiles crashes however at runtime with this error message:
`ReferenceError: Must call super constructor in derived class before accessing 'this' or returning from derived constructor`

The error lies in the generated `__awaiter` function trying to access `this`. The traditional function wraps the `__awaiter` call (therefore binding its own `this`) not causing it to fail.

### 🙂 Expected behavior

Print `Hello` to the console.