sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: mouse without bowders doesnt work
Labels: Issue-Bug,Needs-Triage,Product-Mouse Without Borders

### Microsoft PowerToys version

0.80.1

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

After the windows 11 auto updated or powertoys updated, the MWB doesn't work, A connect B, the state color is yellow, B connect A, the state color is blue.
[PowerToysReport_2024-04-25-12-17-19.zip](https://github.com/microsoft/PowerToys/files/15104034/PowerToysReport_2024-04-25-12-17-19.zip)
<img width="1429" alt="image" src="https://github.com/microsoft/PowerToys/assets/29687593/5cdd034b-bc79-4199-bb14-52320eefb9ec">
![image](https://github.com/microsoft/PowerToys/assets/29687593/667d6296-308c-4985-91ed-1b97da85d945)


### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: rust
Issue: compiletest: Support aux-bin with cross compilation
Labels: A-testsuite,E-hard,C-enhancement,A-cross,T-bootstrap,A-compiletest

### Step-by-step

1. `src/ci/docker/run.sh --dev armhf-gnu`
2. `../x test --target arm-unknown-linux-gnueabihf tests/ui/compiletest-self-test/test-aux-bin.rs`

(Watch out for the problem fixed in https://github.com/rust-lang/rust/pull/124359.)

### Expected

The test is run through the existing remote-test-client / remote-test-server mechanism and passes.

### Actual

It is ignored because aux-bin does not work for this case yet:

```
running 1 tests
test [ui] tests/ui/compiletest-self-test/test-aux-bin.rs ... ignored, ignored when cross-compiling (because aux-bin does not yet support it)
```

### The problem

The problem is simply that the existing remote-test-client / remote-test-server mechanism has not been taught how to deal with aux-bin files.

### Compare with

If you run the test without cross compilation it works:

```console
$ ./x test tests/ui/compiletest-self-test/test-aux-bin.rs
running 1 tests
test [ui] tests/ui/compiletest-self-test/test-aux-bin.rs ... ok
```

### Other info

I was asked [here](https://github.com/rust-lang/rust/pull/123316#discussion_r1577079412) to file this issue.
Repository: tauri
Issue: [bug] tauri V2 updater InvalidSignature
Labels: type: bug,status: needs triage

### Describe the bug

When I use the updater function, it has triggered the check. Then I use update.downloadAndInstall and the download completes, but the error `Uncaught (in promise) InvalidSignature` is returned.
I first used the release address of github, and then I used a separate https domain name to test, but the same error was reported.
![image](https://github.com/tauri-apps/tauri/assets/33891067/740be3d4-22a8-4175-8e2f-52d891fe4cfe)
![image](https://github.com/tauri-apps/tauri/assets/33891067/b5caeb09-1a38-4101-8224-da430670bfd2)

### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
[✔] Environment
    - OS: Windows 10.0.22631 X64
    ✔ WebView2: 123.0.2420.97
    ✔ MSVC: Visual Studio Enterprise 2022
    ✔ rustc: 1.76.0 (07dca489a 2024-02-04)
    ✔ cargo: 1.76.0 (c84b36747 2024-01-18)
    ✔ rustup: 1.27.0 (bbb9276d2 2024-03-08)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 20.9.0
    - pnpm: 8.15.4
    - yarn: 1.22.22
    - npm: 10.1.0

[-] Packages
    - tauri [RUST]: 2.0.0-beta.16
    - tauri-build [RUST]: 2.0.0-beta.13
    - wry [RUST]: 0.39.2
    - tao [RUST]: 0.27.1
    - @tauri-apps/api [NPM]: 2.0.0-beta.6
    - @tauri-apps/cli [NPM]: 2.0.0-beta.10

[-] App
    - build-type: bundle
    - CSP: default-src 'self' customprotocol: asset:; style-src 'unsafe-inline' 'self' 'nonce-10500982406343687894' 'nonce-9786197052427597798'; connect-src ipc: http://ipc.localhost ws:; script-src 'self' 'unsafe-eval' 'sha256-f2aYrerT20WDJlPe3kdN3JfQlyKoRxP33xkWfDbeO9I=' 'sha256-GFebPxKzs1UkFRCbyMaykyYD7rGVWnt1zk1m6r+ZTWQ=' 'sha256-iUqSk0LHeoYfdwsQNbveDMYkU7Tq/OmyauSlE3snBuc='; font-src https://fonts.gstatic.com http://tauri.localhost; img-src 'self' blob: data: http: https: asset: http://asset.localhost
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: Vue.js
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: ollama
Issue: Model Pooling and Instance Management
Labels: feature request

This builds on from model concurrency (#3418), and the `keep_alive` option.

First of all it would be great to be able to load multiple instances of the _same_ model, if I'm not mistaken the model concurrency only works for different models.

Of course loading multiple instances would require a new way of managing them since each model name could refer to many instances - therefore instances should be identifiable.

In addition to this having more methods to be able to get the state of the system is important, here are some suggestions of what a user might want to do:
- Get the ID of a model instance (when generating or preloading).
- List the models/instances currently loaded into memory.
- Get information about each instance (keep_alive, expiry, queue length, RAM/VRAM usage etc.)
- Unload specific instances from memory.
- Queue requests to any instance of a model.
- Queue requests to a particular instance of a model.

My specific use case is that I have different models for different applications (multi-modal LLM, smarter LLM, faster LLM, etc.) and I would like to have (if possible - dynamic) pools of these models so each model has several instances and can manage multiple concurrent requests on the same machine similar to a thread pool.

References:
- https://github.com/ollama/ollama/pull/3418
- https://github.com/ollama/ollama/issues/2431
- https://github.com/ollama/ollama/blob/main/docs/faq.md#how-can-i-pre-load-a-model-to-get-faster-response-times
Repository: react-native
Issue: TypeError: Cannot create property 'lastUpdateCheck' on string 'lastUpdateCheck 1713956001921 nodeLinker node-modules ces nodeLinker node-modules'
Labels: Needs: Triage :mag:,Needs: Repro,Needs: Attention

### Description

Got TypeError while creating app with latest version.  

### Steps to reproduce

1. npx react-native@latest init MyProject

### React Native Version

0.74.0

### Affected Platforms

Runtime - Android, Runtime - iOS

### Output of `npx react-native info`

```text
System:
  OS: macOS 14.3.1
  CPU: (8) arm64 Apple M2
  Memory: 82.64 MB / 8.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.12.1
    path: /usr/local/bin/node
  Yarn:
    version: 1.22.22
    path: /usr/local/bin/yarn
  npm:
    version: 10.5.0
    path: /usr/local/bin/npm
  Watchman: Not Found
Managers:
  CocoaPods:
    version: 1.15.2
    path: /usr/local/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.2
      - iOS 17.2
      - macOS 14.2
      - tvOS 17.2
      - visionOS 1.0
      - watchOS 10.2
  Android SDK: Not Found
IDEs:
  Android Studio: 2023.2 AI-232.10300.40.2321.11567975
  Xcode:
    version: 15.2/15C500b
    path: /usr/bin/xcodebuild
Languages:
  Java: Not Found
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.74.0
    wanted: 0.74.0
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false
```


### Stacktrace or Logs

```text
TypeError: Cannot create property 'lastUpdateCheck' on string 'lastUpdateCheck 1713956001921 nodeLinker node-modules ces nodeLinker node-modules'
    at /Users/kuldip/Documents/RN-Projects/Chat-RN/FirebaseChat/.yarn/releases/yarn-1.22.22.cjs:100249:32
    at Generator.next (<anonymous>)
    at step (/Users/kuldip/Documents/RN-Projects/Chat-RN/FirebaseChat/.yarn/releases/yarn-1.22.22.cjs:310:30)
    at /Users/kuldip/Documents/RN-Projects/Chat-RN/FirebaseChat/.yarn/releases/yarn-1.22.22.cjs:328:14
    at new Promise (<anonymous>)
    at new F (/Users/kuldip/Documents/RN-Projects/Chat-RN/FirebaseChat/.yarn/releases/yarn-1.22.22.cjs:25832:28)
    at /Users/kuldip/Documents/RN-Projects/Chat-RN/FirebaseChat/.yarn/releases/yarn-1.22.22.cjs:307:12
    at YarnRegistry.saveHomeConfig (/Users/kuldip/Documents/RN-Projects/Chat-RN/FirebaseChat/.yarn/releases/yarn-1.22.22.cjs:100253:7)
    at /Users/kuldip/Documents/RN-Projects/Chat-RN/FirebaseChat/.yarn/releases/yarn-1.22.22.cjs:7440:38
    at Generator.next (<anonymous>)
```


### Reproducer

https://github.com/facebook/react-native

### Screenshots and Videos

_No response_
Repository: rust
Issue: Incorrect direction/place for "returning this value requires that `<variable>` is borrowed for `'static`" for E0597
Labels: A-diagnostics,A-borrow-checker,T-compiler

### Code

```Rust
#[derive(Debug)]
pub struct Report(Vec<Box<dyn std::fmt::Debug>>);

fn main() -> Result<(), Report> {
    let string = "".to_string();
    let (_, b) = string
        .split(' ')
        .filter_map(|x| x.split_once(' '))
        .last()
        .unwrap();
    b.split_once(' ').ok_or_else(|| Report(vec![Box::new(b)]))?;
    Ok(())
}
```


### Current output

```Shell
error[E0597]: `string` does not live long enough
  --> test.rs:6:18
   |
5  |     let string = "".to_string();
   |         ------ binding `string` declared here
6  |     let (_, b) = string
   |                  ^^^^^^ borrowed value does not live long enough
7  |         .split(' ')
8  |         .filter_map(|x| x.split_once(' '))
   |                         ----------------- returning this value requires that `string` is borrowed for `'static`
...
13 | }
   | - `string` dropped here while still borrowed

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0597`.
```


### Desired output

```Shell
error[E0597]: `string` does not live long enough
  --> test.rs:6:18
   |
5  |     let string = "".to_string();
   |         ------ binding `string` declared here
6  |     let (_, b) = string
   |                  ^^^^^^ borrowed value does not live long enough
...
11 |     b.split_once(' ').ok_or_else(|| Report(vec![Box::new(b)]))?;
   |                                                          ^    - `string` dropped here while still borrowed
   |                                                          |
   |      returning this value requires that `string` is borrowed for `'static`

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0597`.

┌──────┐
│  OR  │
└──────┘

error[E0515]: cannot return value referencing local variable `string`
  --> test.rs:11:63
   |
6  |     let (_, b) = string
   |                  ------ `string` is borrowed here
...
11 |     b.split_once(' ').ok_or_else(|| Report(vec![Box::new(b)]))?;
   |                                                               ^ returns a value referencing data owned by the current function

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0515`.
```


### Rationale and extra context

_No response_

### Other cases

```Rust
This error message look me quite a while to reproduce, so it seems to be pretty specific with the structure of `Option<Option<…>>`.

Changing `ok_or_else` to `ok_or` causes the same error.
```


### Rust Version

```Shell
rustc 1.77.0 (aedd173a2 2024-03-17)
binary: rustc
commit-hash: aedd173a2c086e558c2b66d3743b344f977621a7
commit-date: 2024-03-17
host: x86_64-unknown-linux-gnu
release: 1.77.0
LLVM version: 17.0.6
```


### Anything else?

_No response_
Repository: pytorch
Issue: Exporting torch slice_scatter to onnx Identity
Labels: module: onnx,triaged

### 🐛 Describe the bug

Hello. I've tried to export an onnx model from the torch module that contains `slice_scatter` and the exported onnx model just contains `Identity`, which seems not valid. Is it intended behavior?

```python
import torch

class SimpleModule(torch.nn.Module):
  def __init__(self):
    super().__init__()

  def forward(self, a, b):
    a.slice_scatter(b, dim=1, start=2, end=6, step=2)
    return a

  def example_inputs(self):
    a = torch.randn(8,8)
    b = torch.randn(8,2)
    return a, b

m = SimpleModule()

torch.onnx.export(m, m.example_inputs(), 'test.onnx')
```

[onnx_model.zip](https://github.com/pytorch/pytorch/files/15105047/test.zip)

### Versions

```
PyTorch version: 2.4.0.dev20240324+cpu
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.6 LTS (x86_64)
GCC version: (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Clang version: 10.0.0-4ubuntu1 
CMake version: version 3.29.2
Libc version: glibc-2.31

Python version: 3.10.4 (main, Apr  4 2024, 18:59:41) [GCC 9.4.0] (64-bit runtime)
Python platform: Linux-5.15.0-102-generic-x86_64-with-glibc2.31
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] executorch==0.1.0
[pip3] flake8==6.0.0
[pip3] flake8-breakpoint==1.1.0
[pip3] flake8-bugbear==23.6.5
[pip3] flake8-comprehensions==3.12.0
[pip3] flake8-plugin-utils==1.3.3
[pip3] flake8-pyi==23.5.0
[pip3] mypy==1.9.0
[pip3] mypy-extensions==1.0.0
[pip3] numpy==1.26.4
[pip3] onnx==1.16.0
[pip3] onnxscript==0.1.0.dev20240425
[pip3] torch==2.4.0.dev20240324+cpu
[pip3] torchaudio==2.2.0.dev20240324+cpu
[pip3] torchsr==1.0.4
[pip3] torchvision==0.19.0.dev20240324+cpu
```
Repository: ant-design
Issue: rangepicker showtime 第一个框时分秒用默认的不点确定，第二个框点确定会导致。选择失败，俩个框都空白
Labels: 🐛 Bug,Inactive



https://github.com/ant-design/ant-design/assets/19306050/e3b994d0-e244-4a6a-818d-c8262966dd28

### Reproduction link

[https://ant.design/components/date-picker-cn#components-date-picker-demo-range-picker](https://ant.design/components/date-picker-cn#components-date-picker-demo-range-picker)

### Steps to reproduce

#### 官网的rangepicker 示例， 第二个 rangepicker
- rangepicker 开启 showtime
- 第一个框，选择日期， 时间采用默认，不点确定。
- 第二个框，选择日期，时间， 点击确定
结果直接一闪而过，俩个框都变空白


### What is expected?

和antd 4 一样， rangepicker第一个框 无需点击确定也能正常选择成功

### What is actually happening?

结果直接一闪而过，俩个框都变空白

| Environment | Info |
| --- | --- |
| antd | 5.16.4 |
| React | 17\18 |
| System | macos |
| Browser | chrome 最新 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: PowerToys
Issue: key mapping bug
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Needs-Triage

### Microsoft PowerToys version

0.80.1

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

i have reassigned my alt key to left but whenever i presses alt  ctrl+left  is the function that is executing

### ✔️ Expected Behavior

 left function should activated

### ❌ Actual Behavior

ctrl+left is executing

### Other Software

_No response_
Repository: go
Issue: x/tools/refactor/eg: 'exec format error' Test failures
Labels: NeedsInvestigation,Tools

```
#!watchflakes
default <- pkg == "golang.org/x/tools/refactor/eg" && test == "Test"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8749724725921955617)):

    === RUN   Test
        eg_test.go:168: eg tests for /Users/swarming/.swarming/w/ir/x/w/targetrepo1490007702/refactor/eg/testdata/A1.go failed: fork/exec /usr/bin/diff: exec format error.
            
        eg_test.go:168: eg tests for /Users/swarming/.swarming/w/ir/x/w/targetrepo1490007702/refactor/eg/testdata/A2.go failed: fork/exec /usr/bin/diff: exec format error.
            
        eg_test.go:168: eg tests for /Users/swarming/.swarming/w/ir/x/w/targetrepo1490007702/refactor/eg/testdata/B1.go failed: fork/exec /usr/bin/diff: exec format error.
            
        eg_test.go:168: eg tests for /Users/swarming/.swarming/w/ir/x/w/targetrepo1490007702/refactor/eg/testdata/C1.go failed: fork/exec /usr/bin/diff: exec format error.
            
        eg_test.go:168: eg tests for /Users/swarming/.swarming/w/ir/x/w/targetrepo1490007702/refactor/eg/testdata/D1.go failed: fork/exec /usr/bin/diff: exec format error.
            
        eg_test.go:168: eg tests for /Users/swarming/.swarming/w/ir/x/w/targetrepo1490007702/refactor/eg/testdata/E1.go failed: fork/exec /usr/bin/diff: exec format error.
            
        eg_test.go:168: eg tests for /Users/swarming/.swarming/w/ir/x/w/targetrepo1490007702/refactor/eg/testdata/F1.go failed: fork/exec /usr/bin/diff: exec format error.
            
        eg_test.go:168: eg tests for /Users/swarming/.swarming/w/ir/x/w/targetrepo1490007702/refactor/eg/testdata/G1.go failed: fork/exec /usr/bin/diff: exec format error.
            
        eg_test.go:168: eg tests for /Users/swarming/.swarming/w/ir/x/w/targetrepo1490007702/refactor/eg/testdata/H1.go failed: fork/exec /usr/bin/diff: exec format error.
            
        eg_test.go:168: eg tests for /Users/swarming/.swarming/w/ir/x/w/targetrepo1490007702/refactor/eg/testdata/I1.go failed: fork/exec /usr/bin/diff: exec format error.
            
        eg_test.go:168: eg tests for /Users/swarming/.swarming/w/ir/x/w/targetrepo1490007702/refactor/eg/testdata/J1.go failed: fork/exec /usr/bin/diff: exec format error.
            
    --- FAIL: Test (9.30s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: ant-design
Issue: RangePicker 在 shadowDom 模式下无法单独修改 end 数据
Labels: 🐛 Bug,Inactive

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/shou-dong-chu-fa-forked-4yz3k8?file=%2FDemo.tsx%3A9%2C14)

### Steps to reproduce

在 shadowDom 节点中使用 RangePicker  组件，无法单独修改 end 时间，会自动挑到 start 时间

### What is expected?

支持单独修改 end 时间

### What is actually happening?

不支持单独修改 end 时间

| Environment | Info |
| --- | --- |
| antd | 5.16.4 |
| React | 18.2.0 |
| System | window |
| Browser | chrome/124.0 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: next.js
Issue: Routes are broken when the page extension contains only 'tsx'.
Labels: bug,Runtime,Pages Router,linear: next,locked

### Link to the code that reproduces this issue

https://github.com/thecuvii/page-extensions-repro

### To Reproduce

1. Create a new TypeScript app.

2. Set `pageExtensions` to `['tsx']` in next.config.js.

3. Visiting `localhost:3000` will result in an error page with the message: 'pageExtensions.map is not a function'.

![CleanShot 2024-04-25 at 7 20 49@2x](https://github.com/vercel/next.js/assets/11806619/f9020634-aea0-45c9-ba20-7f129be44828)

4. Set pageExtension to `['tsx', 'ts'] and the problem will be resolved.

### Current vs. Expected behavior

The router works when the `pageExtensions` are set to `['tsx']`.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.4.0: Fri Mar 15 00:10:42 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6000
  Available memory (MB): 65536
  Available CPU cores: 10
Binaries:
  Node: 20.12.2
  npm: 10.5.0
  Yarn: N/A
  pnpm: 9.0.5
Relevant Packages:
  next: 14.2.3 // Latest available version is detected (14.2.3).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Pages Router, Runtime

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

_No response_

<sub>[NEXT-3244](https://linear.app/vercel/issue/NEXT-3244/routes-are-broken-when-the-page-extension-contains-only-tsx)</sub>
Repository: deno
Issue: Panic when passing wildcard to allow-net
Labels: bug,cli

Platform: linux x86_64
Version: 1.42.1
Args: ["deno", "run", "--allow-read", "--allow-write=notion-next", "--allow-net=api.notion.com,*.amazonaws.com", "--allow-env", "main.ts"]

thread 'main' panicked at runtime/permissions/lib.rs:741:22:
called `Result::unwrap()` on an `Err` value: InvalidLabelChar
Repository: vscode
Issue: Add Title Menu Entry for Extensions
Labels: feature-request,menus

<!-- ⚠️⚠️ 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 have an extension in VS Code and I would like to add a context menu item to the VS Code Menu panel (File, View, Edit ...) related to my extention. 

There could be an extra option called "Extension" like in Atom mentioned here : [#6000](https://github.com/microsoft/vscode/pull/6000) or under Edit maybe. The former makes more sense though.

I understand that this was asked for, long back, and there is no addition of this feature yet but it seems quite helpful.
Also there is quite a demand for it : [#365](https://github.com/microsoft/vscode/issues/365)
Repository: puppeteer
Issue: [Feature]: Request Initiator Chain
Labels: feature,P3

### Feature description

Hi,

This is to request information such as "**Initiator Chain**" for each request that is currently present in the Initiator section in Chrome Network tab:
![Network Tab](https://github.com/puppeteer/puppeteer/assets/35270649/11e3587f-93e0-4393-a4e1-76a4aef54815)

Currently, it is possible to get the immediate [initiator](https://chromedevtools.github.io/devtools-protocol/tot/Network/#type-Initiator) for an initial request via request events but not the complete initiator chain. It is further limited by type of initiator and only information for "Parser" and "Script" type requests are present, making it difficult to reliably generate this tree either. (Related discussions [here](https://github.com/puppeteer/puppeteer/issues/1395#issuecomment-1908172112))

While this is discussed and implemented, I would be happy to try out some alternates (maybe with CDP which exposes a little more information in some cases)?
Repository: pytorch
Issue: Missing description of Transformer argument "memory_mask" shape in 3D (including the batch dimension) case
Labels: module: nn,triaged

### 📚 The doc issue

`nn.TransformerDecoder` seems to support 3D (N*nhead, T, S) memory_mask (since https://github.com/pytorch/pytorch/issues/32590#issue-554929072), and the description of `nn.MultiheadAttention` has been updated correctly. But the description of `nn.Transformer` argument memory_mask's shape (https://pytorch.org/docs/stable/generated/torch.nn.Transformer.html#torch.nn.Transformer, v2.3) missed 3D input case. 

### Suggest a potential alternative/fix

Add description of "(N*num_heads, T, S)" for 3D memory_mask inputting case.

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki @bhosmer @cpuhrsch @erichan1 @drisspg