sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: terminal
Issue: Add fine-grained mouse report configurability like iTerm2
Labels: Issue-Feature,Area-TerminalControl,Area-Settings,Product-Terminal

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

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

First of all: congrats on the tmux support you have so far, it's pretty great already out of the box!
Lots of things "just work" right away, including with mouse reporting:
- using the mouse wheel works great (with the usual/typical tmux copy-mode)
- mouse reporting works perfectly well in tools like `vim`
- I was able to even easily make my favorite tmux window navigation shortcut work with this in my settings:

```
{ "command": {"action": "sendInput", "input": "\u001b[1;3C" }, "keys": "alt+right" },
{ "command": {"action": "sendInput", "input": "\u001b[1;3D" }, "keys": "alt+left" },
```

Where it's not working well unfortunately is when trying to simply select some text while under tmux (ie: simply click+drag -> nothing happens).
Mouse reporting also does not work outside of tools like `vim` (ie: click on a tmux pane or window -> nothing happens)

Usually with tmux, when mouse reporting is completely transferred to tmux, then one can switch panes/windows by clicking (but one does lose the click+drag usual text selection method in that case).

My favorite mode with tmux integration is something that latest iTerm2 does on macos: one can enable mouse reporting for tmux, but limit it to wheel events only. That way, I can:
- use click+drag to select text (as-if tmux wasn't running at all)
- use mouse wheel to trigger the copy-mode in tmux and scroll through tmux output history (this works perfectly well currently in WindowsTerminal!)

# Proposed technical implementation details (optional)

Feature request: can you make it so that one can choose to pass through mouse wheel events only to tmux?
Perhaps a new optional setting such as:
```
"mouseReporting": "enabled|disabled|wheelOnly"
```
Repository: go
Issue: proposal: testing: relax lower-case suffix requirement for example test annotation
Labels: Proposal

### Background

The testing package provides a mechanism to produce distinct examples for a single package, function, type or method.

> Multiple example functions for a package/type/function/method may be provided by appending a distinct suffix to the name. The suffix must start with a lower-case letter.
>
> ```
> func Example_suffix() { ... }
> func ExampleF_suffix() { ... }
> func ExampleT_suffix() { ... }
> func ExampleT_M_suffix() { ... }
> ```

Currently, this is specified to be defined by a suffix that starts with a lower-case letter. This restrictions is presumably to ensure that a method (which must start with an upper-case letter to be justified in having a documentation example by virtue of being exported) is distinguishable from a suffix tag. The godoc command has always allowed numeric and first characters, enabling the use of culturally conventional numbered examples and use of 'words' that start with a number (see #43454 for the motivation for this proposal). It's worth noting that the only requirement for distinguishing between a method `_M` and a human-directed `_suffix` would be that the suffix can not be interpretable as a method worth documenting; it must not have an upper-case initial.

### Proposal

Relax the documented restriction to be "The suffix must not start with an upper-case letter."
Repository: excalidraw
Issue: add UI to open collaboration links from PWAs
Labels: enhancement,discussion

See https://github.com/excalidraw/excalidraw/discussions/2712
Repository: pytorch
Issue: torch.where scalar/tensor documentation is unclear and not formatted
Labels: module: docs,triaged,module: sorting and selection

## 📚 Documentation

See:
`
Currently valid scalar and tensor combination are 1. Scalar of floating dtype and torch.double 2. Scalar of integral dtype and torch.long 3. Scalar of complex dtype and torch.complex128
`

I believe these are supposed to be on separate lines.  Also this message comes before the type information, it's not clear what. "scalar and tensor combination" are.  It should at least mention it's talking about `x` and `y` and not `condition`.


<!-- A clear and concise description of what content in https://pytorch.org/docs is an issue. If this has to do with the general https://pytorch.org website, please file an issue at https://github.com/pytorch/pytorch.github.io/issues/new/choose instead. If this has to do with https://pytorch.org/tutorials, please file an issue at https://github.com/pytorch/tutorials/issues/new -->


cc @jlin27 @mruberry @heitorschueroff
Repository: excalidraw
Issue: Ask to save unsaved changes before closing
Labels: enhancement

When I open a `.excalidraw` file from the [file manager](https://github.com/excalidraw/excalidraw/discussions/2714) in a PWA (created by the Brave browser), then make a few changes and close the PWA, then the changes aren't saved to the `.excalidraw` file. So before closing the PWA I have to manually save it by `ctrl+s`, but I would prefer, if upon closing the PWA a window would pop up asking to save the latest changes.
Repository: pytorch
Issue: [proposal] Pseudo-functions to support common gradient patch use-cases like replacing inf / nan, gradient clipping / reversal
Labels: module: autograd,triaged,needs design

Created per @alband request.

Originally started in https://github.com/pytorch/pytorch/issues/31829#issuecomment-754939837 and in  https://github.com/pytorch/pytorch/issues/35666#issuecomment-606826976

Motivations: these gradient hacks are quite common and not completely trivial, should be nice to have them in core as idioms

In addition, having a convenience function to replace some inf/nan by passed values in forward pass would be good as well (especially if it mirrors the API of the gradient pseudo-function).

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer
Repository: deno
Issue: Implement WebTransport (QUICTransport) API
Labels: suggestion,runtime

Once we have [QUIC](https://github.com/denoland/deno/issues/3995) support implemented, we should consider implementing the [WebTransport API](https://github.com/w3c/webtransport).

A long way to go, but just to have a place for discussions for this feature.

More informations:
- https://web.dev/webtransport/
Repository: vscode
Issue: Breadcrumb supports expend all level by default
Labels: feature-request,breadcrumbs

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
I want to search all symbol in current file, but Breadcrumb only show symbols that have expend already.
![image](https://user-images.githubusercontent.com/24750337/103718463-c2e66300-5001-11eb-9258-3e460a6fe301.png)

Compare to Jetbrains's IDE, it expend all level by default :)
![image](https://user-images.githubusercontent.com/24750337/103718633-2e303500-5002-11eb-8377-40f195213ba7.png)

This feature is convenient for us to quick search symbol
Repository: rust
Issue: Infinite loop when trying to fill a Vector of MaybeUninit<SomeZeroSizedType>
Labels: A-collections,T-libs-api,A-docs

I tried to reduce the demonstration to the minimum possible.

I wrote a function that fills a vector of `MaybeUninit<T>` values that I think is safe (free of UB).
The code works well with `cargo miri run`.

But when calling this function with a zero-sized type, the execution goes into an infinite loop.
The exact same code without the `MaybeUninit` logic works as expected.

Here is the code:

```rust
#![feature(maybe_uninit_extra)] // not important, works also without
use core::mem::{self, MaybeUninit};

struct A(u8);
impl Default for A {
    fn default() -> Self {
        Self(0)
    }
}
impl Drop for A {
    fn drop(&mut self) {
        println!("dropping A");
    }
}

struct B;
impl Default for B {
    fn default() -> Self {
        Self
    }
}
impl Drop for B {
    fn drop(&mut self) {
        println!("dropping B");
    }
}

// Fills a vector of uninitialized T with their default values
fn fill_default_uninit<T: Default>(mut v: Vec<MaybeUninit<T>>) -> Vec<T> {
    v.iter_mut().for_each(|i|{
        i.write(T::default()); // without the nightly feature: unsafe{i.as_mut_ptr().write(T::default())};
    });
    unsafe { mem::transmute::<_, _>(v) } // this is safe because the Vec is now fully initialized
}

// Fills a vector of T with their default values, overriding the previous ones
fn fill_default_init<T: Default>(mut v: Vec<T>) -> Vec<T> {
    v.iter_mut().for_each(|i|{
        *i = T::default();
    });
    v
}

fn main() {
    // create an uninitialized vector of 3 As
    let mut v: Vec<MaybeUninit<A>> = Vec::with_capacity(3);
    unsafe{v.set_len(v.capacity())}; // this is safe because the elements are MaybeUninit
    let v = fill_default_uninit(v); // no problem
    drop(v); // all 3 As are dropped
    
    
    // create an uninitialized vector of 3 Bs
    let mut v: Vec<MaybeUninit<B>> = Vec::with_capacity(3);
    unsafe{v.set_len(v.capacity())}; // this is safe because the elements are MaybeUninit
    //let v = init_default(v); //  <------------------------------------------------------ INFINITE LOOP HERE
    //drop(v);
    
    // now let's try the same code for B without MaybeUninit
    let mut v = Vec::with_capacity(3);
    for _ in 0..3 { v.push(B::default()) }

    let v = fill_default_init(v); // no problem, here the 3 old Bs will be dropped
    drop(v); // no problem, the 3 new Bs will be dropped
}
```

([Playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=10c5cfb3d94ca617fec24da260006ca0))

Output:

```
dropping A
dropping A
dropping A
dropping B
dropping B
dropping B
dropping B
dropping B
dropping B

```
Repository: pytorch
Issue: JIT does not correctly compile custom classes derived from torch.Tensor
Labels: oncall: jit

## 🐛 Bug

In the unlikely case of user defining a custom class that derives `torch.Tensor`, TorchScript would still treat it like base `torch.Tensor` class, which can lead to incorrect behavior.

## To Reproduce

Steps to reproduce the behavior:

```
import torch

class TensorSubClass(torch.Tensor):
    def __init__(self, x: torch.Tensor):
        super().__init__()
        self.x = x

    def __len__(self):
        return 123456


def fn(x: TensorSubClass):
    return len(x)

x = TensorSubClass(torch.rand((2, 3, 4)))
length_from_eager = fn(x)

scripted_fn = torch.jit.script(fn)
length_from_jit = scripted_fn(x)

if length_from_eager != length_from_jit:
    print("Eager and jit behavior mismatching: %d vs %d" % (length_from_eager, length_from_jit))
else:
    print("Eager and jit behavior match, both are: %d" % length_from_jit)
```

## Expected behavior

Expecting that JIT and eager produce same result or JIT explicitly rejecting user's custom class.



cc @gmagogsfm
Repository: create-react-app
Issue: Cannot debug production build of react app in VSCode
Labels: needs triage,issue: bug report

<!--
    Please note that your issue will be fixed much faster if you spend about
    half an hour preparing it, including the exact reproduction steps and a demo.

    If you're in a hurry or don't feel confident, it's fine to report bugs with
    less details, but this makes it less likely they'll get fixed soon.

    In either case, please use this template and fill in as many fields below as you can.

    Note that we don't provide help for webpack questions after ejecting.
    You can find webpack docs at https://webpack.js.org/.
-->

### Describe the bug

Cannot debug production build of react app in VSCode, repro steps:

1. Create a simple react app using the command below
```
 npx create-react-app my-app
```
2. Open the project in VSCode, and add launch.json file:
```
        {
            "name": "Debug (Chrome)",
            "type": "chrome",
            "request": "launch",
            "url": "https://localhost:3000/index.html#/tab",
            "webRoot": "${workspaceFolder}"
        }
``` 

3. Build and run the react script:
```
npm run build
serve build
```

4. Click F5 and try to debug the project

```
The break point is not hit
```


**Other information:**

1. If I am using development build as below, then I can hit the break point

```
npm run start
```

2. I also investigate the build script using the command below
```
react-script eject
```
And if I change the webpack.config.js file from:
```
devtoolModuleFilenameTemplate: isEnvProduction
        ? info =>
            path
              .relative(paths.appSrc, info.absoluteResourcePath)
              .replace(/\\/g, '/')
        : isEnvDevelopment &&
          (info => path.resolve(info.absoluteResourcePath).replace(/\\/g, '/')),
```

to

```
devtoolModuleFilenameTemplate: info => path.resolve(info.absoluteResourcePath).replace(/\\/g, '/');
```

Then I can hit the break point
Repository: opencv
Issue: QTest module causes window program compiler error
Labels: question (invalid tracker),category: build/install,category: 3rdparty

##### System information (version)

- OpenCV =>4.5.1 static library
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2019

##### Detailed description

In opencv highgui module, window_QT.cpp / line 2168 use QTest mudule because **_QTest::keyToAscii(qtkey)_**.
So I must add QTest mudule to my project, but QTest only can use in console application, if I add QTest to window application will cause a compiler error.
May remove the dependency on QTest module? OpenCV just use it only once.

`//Need more test here !
void CvWindow::keyPressEvent(QKeyEvent *evnt)
{
    //see http://doc.trolltech.com/4.6/qt.html#Key-enum
    int key = evnt->key();

        Qt::Key qtkey = static_cast<Qt::Key>(key);
        char asciiCode = QTest::keyToAscii(qtkey);
        if (asciiCode != 0)
            key = static_cast<int>(asciiCode);
        else
            key = evnt->nativeVirtualKey(); //same codes as returned by GTK-based backend

    //control plus (Z, +, -, up, down, left, right) are used for zoom/panning functions
        if (evnt->modifiers() != Qt::ControlModifier)
        {
        mutexKey.lock();
        last_key = key;
        mutexKey.unlock();
        key_pressed.wakeAll();
        //evnt->accept();
    }`

 **compiler error:**
`LIBCMT.lib(exe_winmain.obj) : error LNK2019: 无法解析的外部符号 WinMain，函数 "int __cdecl __scrt_common_main_seh(void)" (?__scrt_common_main_seh@@YAHXZ) 中引用了该符号`
Repository: pytorch
Issue: nn.InstanceNorm should warn user if input channel is inconsistent with num_features, even when affine=False
Labels: module: nn,triaged,needs design,module: norms and normalization

## 🐛 Bug

When `nn.InstanceNorm1d` is used without affine transformation, it does not warn the user even if the channel size of input is inconsistent with `num_features` parameter. Though the `num_features` won't matter on computing `InstanceNorm(num_features, affine=False)`, I think it should warn the user if the wrong argument/input is being given.

## To Reproduce & Expected behavior

```python
import torch
import torch.nn as nn

# we define an InstanceNorm1d layer without affine transformation, where num_features=7
# note that affine is set False by default
m = nn.InstanceNorm1d(7)

# here, the input with the wrong channel size (3) is given.
input = torch.randn(2, 3, 5)

# the following operation should warn the user, although there's no problem with performing the computation.
output = m(input)
```

I'm not sure whether this is intended behavior or not.

## Environment

PyTorch version: 1.7.0+cu110
Is debug build: True
CUDA used to build PyTorch: 11.0
ROCM used to build PyTorch: N/A

OS: Microsoft Windows 10 Pro
GCC version: (MinGW.org GCC-8.2.0-3) 8.2.0
Clang version: Could not collect
CMake version: version 3.14.3

Python version: 3.6 (64-bit runtime)
Is CUDA available: True
CUDA runtime version: Could not collect
GPU models and configuration: GPU 0: GeForce RTX 2060
Nvidia driver version: 460.89
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip3] numpy==1.19.3
[pip3] pytorch-lightning==1.0.3
[pip3] pytorch-ranger==0.1.1
[pip3] torch==1.7.0+cu110
[pip3] torch-optimizer==0.0.1a15
[pip3] torchvision==0.8.1+cu110
[conda] Could not collect

cc @albanD @mruberry @jbschlosser
Repository: ant-design
Issue: [Tabs] Not able to scroll tab bar if tabPosition = left/right in iPad
Labels: Inactive

- [x] 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/position-antd4100-forked-4rbmd?file=/index.js)

### Steps to reproduce
- Set `tabPosition` to left or right
- Make tab bar overflow
- Try scroll down tab bar

### What is expected?
If tab bar is overflowed, it should be scrollable and there should be a more icon under the tab bar

### What is actually happening?
Not able to scroll the tab bar and the more icon is not appeared

| Environment | Info |
|---|---|
| antd | 4.10.0 |
| React | 16.14.0 |
| System | iPadOS 13.7 |
| Browser | Safari 13 |


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: pytorch
Issue: Inconsistent Variable Naming in FindTorch.cmake
Labels: module: build,module: cpp,triaged

## 🐛 Bug

when find_package'ing Torch in C++ environments, CMake variables like `_LIBRARIES` or `_INCLUDE_DIRS` are set uppercase (`TORCH_`) instead of being set according to the package name (`Torch_`), which is at least common practice in other packages (e.g. [Boost](https://cmake.org/cmake/help/latest/module/FindBoost.html) ).

Although not rendering the package inusable, at least in my case this leads to problems when automatically resolving dependencies between packages, as the set variables are not directly tied to the package name. Furthermore, usage of this package was not as straightforward as it could have been.

cc @malfet @seemethere @walterddr @yf225 @glaringlee
Repository: bitcoin
Issue: Restrict RPCs that make server-side files
Labels: RPC/REST/ZMQ

Currently `dumpwallet` (and other RPCs that create server-side files) can scribble all over the file system, at least as the user running `bitcoind` permits.

It would be better if these were at the least limited to the data directory, or even a specific directory within the data directory, say, `~/.bitcoin/dumpwallet`—to avoid name collisions with wallets, lock files and database files. Overwriting is already prevented.

(Issue originally reported by Florian Mathieu)
Repository: create-react-app
Issue: A  generator function's problem
Labels: needs triage,issue: bug report

Hi~ guys

I am puzzled by a problem，here is a mini [repo](https://github.com/fidoChou/ABadCase) to reproducible。

1. I  used the 「react-scripts」 to start the server,
	just clone && yarn && yarn start

2. In the App.js,  a.b.constructor.name === 'Function'
	but the c.b.constructor.name === 'GeneratorFunction'

	I am really dont know what happened :(

	```
	 const a = {
	    * b() {}
	  }
         const c = {
	    b: function*() {}
	  }

	{a.b.constructor.name} | {c.b.constructor.name
	```
3. Chrome console is not reproduce
4. Use CRA CLI is  not reproduce

### Environment

node verison: v12.20.0
MacOS: 10.15.6

sorry if disturbed
Repository: go
Issue: binary: expose overflow error
Labels: NeedsDecision,FeatureRequest

At the moment it is not possible to distinguish I/O errors from encoding errors with `binary.ReadUvarint` and `binary.ReadVarint`. The documentation could mention that an overflow is the only encoding error option.
Repository: excalidraw
Issue: Autosave support
Labels: enhancement

When you open/load a file using the new FS, we should support opt-in autosaving during the editing session.

Upon close, if changes aren't saved, it should nevertheless prompt to save changes (https://github.com/excalidraw/excalidraw/issues/2728) regardless of the opt-in status.
Repository: rust
Issue: Boxing zeroed arrays and slices uses `rust_alloc` + `memset` instead of `rust_alloc_zeroed`
Labels: C-enhancement,T-compiler,T-opsem,A-box

```rust
#![feature(box_syntax)]

use std::convert::TryInto;

const N: usize = 100_000;

pub fn foo1() -> Vec<u32> {
    vec![0; N]
}

pub fn foo2() -> Box<[u32]> {
    box [0; N]
}

pub fn foo3() -> Box<[u32; N]> {
    box [0; N]
}

pub fn foo4() -> Box<[u32; N]> {
    vec![0; N].into_boxed_slice().try_into().unwrap()
}
```

Gives (rustc 1.51.0-nightly 80184183b 2021-01-03):

```asm
.LCPI0_0:
    .quad   100000
    .quad   100000
foo1:
    push    rbx
    mov     rbx, rdi
    mov     edi, 400000
    mov     esi, 4
    call    qword ptr [rip + __rust_alloc_zeroed@GOTPCREL]
    test    rax, rax
    je      .LBB0_1
    mov     qword ptr [rbx], rax
    vmovaps xmm0, xmmword ptr [rip + .LCPI0_0]
    vmovups xmmword ptr [rbx + 8], xmm0
    mov     rax, rbx
    pop     rbx
    ret
.LBB0_1:
    mov     edi, 400000
    mov     esi, 4
    call    qword ptr [rip + alloc::alloc::handle_alloc_error@GOTPCREL]
    ud2


foo2:
    push    rbx
    mov     edi, 400000
    mov     esi, 4
    call    qword ptr [rip + __rust_alloc@GOTPCREL]
    test    rax, rax
    je      .LBB1_1
    mov     rbx, rax
    mov     edx, 400000
    mov     rdi, rax
    xor     esi, esi
    call    qword ptr [rip + memset@GOTPCREL]
    mov     edx, 100000
    mov     rax, rbx
    pop     rbx
    ret
.LBB1_1:
    mov     edi, 400000
    mov     esi, 4
    call    qword ptr [rip + alloc::alloc::handle_alloc_error@GOTPCREL]
    ud2


foo3:
    push    rbx
    mov     edi, 400000
    mov     esi, 4
    call    qword ptr [rip + __rust_alloc@GOTPCREL]
    test    rax, rax
    je      .LBB2_1
    mov     rbx, rax
    mov     edx, 400000
    mov     rdi, rax
    xor     esi, esi
    call    qword ptr [rip + memset@GOTPCREL]
    mov     rax, rbx
    pop     rbx
    ret
.LBB2_1:
    mov     edi, 400000
    mov     esi, 4
    call    qword ptr [rip + alloc::alloc::handle_alloc_error@GOTPCREL]
    ud2


foo4:
    push    rax
    mov     edi, 400000
    mov     esi, 4
    call    qword ptr [rip + __rust_alloc_zeroed@GOTPCREL]
    test    rax, rax
    je      .LBB3_1
    pop     rcx
    ret
.LBB3_1:
    mov     edi, 400000
    mov     esi, 4
    call    qword ptr [rip + alloc::alloc::handle_alloc_error@GOTPCREL]
    ud2    
```

I think box should use rust_alloc_zeroed instead.