sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: [elastic/distributed] API to retrieve consolidated worker information
Labels: oncall: distributed,better-engineering,pt_distributed_rampup,oncall: r2p

## 🚀 Feature

When using torch.distributed.launch or torchrun, the spawned worker is created with a given rank, master addr, master port etc. Sometimes printing this information out is useful for debugging hang/connection issues, but currently requires manually parsing the env variables here with https://pytorch.org/docs/stable/elastic/run.html#launcher-api with os.environ

Instead, we can provide a clean API such as 
```
torch.distributed.elastic.get_worker_info() -> Dict[str, Any]
```

that will return a dictionary of useful information such as world size, local rank, master address, hostname, etc to make the debugging process a lot cleaner.

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang
Repository: vscode
Issue: Git - Sync Changes button pushes to different branch than current branch
Labels: bug,git

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
Version: 1.62.3 (user setup)
Commit: ccbaa2d27e38e5afa3e5c21c1c7bef4657064247
Date: 2021-11-17T08:11:14.551Z
Electron: 13.5.2
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19043

Steps to Reproduce:

1. Clone a repository containing a submodule that points to a branch of the submodule's repo.
2. Force recreate the branch based on `main` with `git switch -C <branch name> origin/main`
3. Make and commit a change.
4. Click the "Sync Changes" button in the Source Control panel

Expected Result:

A dialog message containing "This action will push and pull commits to and from `origin/<branch name>`", followed by VS Code pushing commits to `origin/<branch name>`.

Actual Result:

A dialog message containing "This action will push and pull commits to and from 'origin/main'", followed by VS Code pushing commits to `origin/main`.

Furthermore, the current branch indicator in the bottom toolbar shows the correct branch, whereas the Sync Changes button triggers a push to a different branch.

![image](https://user-images.githubusercontent.com/88163/142957461-765b572f-7b2a-4663-978f-12b0e503b961.png)
Repository: pytorch
Issue: [FSDP] Wrap API improvements
Labels: triaged,module: fsdp

## 🚀 Feature

Some follow up work to https://github.com/pytorch/pytorch/pull/68155:

- [x] Remove `auto_wrap()` entirely. The main API for manual wrapping we will support is `enable_wrap()` context manager which is passed the FSDP config, and a nonrecursive `wrap()` function which wraps if we are in the context manager. 
- [ ] Make it easier to use policies for wrapping etc. i.e. provide a wrap_policies class with functions for common policies (such as # of parameters).
- [ ] Update lightning/other callsites to use new FSDP wrap API --> this will help us uncover any shortcomings in the API. Update all tests as well.
- [x] Eliminate support for `module.wrapper_config`. Current code supports this but there are no use cases we are aware of that can't make use of the currently supported APIs, so best to get rid of this and add it back if necessary later. 
- [x] https://github.com/pytorch/pytorch/issues/73809
- [ ] https://github.com/pytorch/pytorch/issues/73767

As a result, for wrapping we are planning to support:

# automatic recursive wrapping of children via a policy
```
FSDP(my_model, fsdp_auto_wrap_policy=default_policy)
```

# Manual wrapping (note that there are no policies or recursion here)

```
with enable_wrap:
    model = wrap(nn.Sequential([wrap(nn.Linear), nn.Linear]))
```


cc @zhaojuanmao @mrshenli @rohan-varma
Repository: transformers
Issue: Add TAPAS trained on NQ
Labels: New model

The authors of the "Open Domain Question Answering over Tables via Dense Retrieval" papers released the weights for TAPAS retriever trained on NQ here: https://github.com/google-research/tapas/blob/master/DENSE_TABLE_RETRIEVER.md

It would be nice if those weights could be converted to Huggingface model (I would presume it's fairly similar the other finetuned model since they share the same architecture, and I'd be happy to do it myself if there's some scripts I can run)
Repository: ant-design
Issue: Tree data may be out of sync with its parent
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/cranky-rhodes-4gq9r?file=/src/App.js)

### Steps to reproduce
1. Expand the only node "foo" of tree, now node "bar" is visible
2. Click "Use After"

### What is expected?
Tree is rendered with a single root "foo", node "bar" disappears

### What is actually happening?
Page crashes with an error "Not found node 2"

| Environment | Info |
|---|---|
| antd | 4.17.1 |
| React | 17.0.2 |
| System | macOS |
| Browser | Chrome 95 |

---
In this sandbox (and our actual business scenarios) we're building tree node content from a custom render function relying on the incoming tree data, however it seems when a node is deleted, there is a chance that ant's Tree will still render a deleted node after its parent has already asynced with a new tree data.

This is a common practice in our business since we have different and complex tree data structures, to keep Tree strongly typed and performant, we build a `TreeHelper` object above the original data structure, all title rendering relies on this helper.


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: pytorch
Issue: Clarify variables of BatchNorm*d functions
Labels: module: docs,module: nn,triaged,needs research,module: norms and normalization,Stale

## 📚 Documentation

https://pytorch.org/docs/stable/generated/torch.nn.BatchNorm1d.html and BatchNorm for higher dimensions reference (but do not define) variables N,C,D,H,W.

I am expecting all variables to be described similar to how https://pytorch.org/docs/stable/generated/torch.nn.RNN.html does.

cc @brianjo @mruberry @albanD @jbschlosser @walterddr @kshitij12345
Repository: TypeScript
Issue: Wired behavior with conditional checking on multiple conditions.
Labels: Bug

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

conditional type on tuple

<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->

### 🕗 Version & Regression Information

v4.5.2


### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior

  The TypeScript Workbench can be used for more complex setups, try
  https://www.typescriptlang.org/dev/bug-workbench/

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground link with relevant code](https://www.typescriptlang.org/play?#code/C4TwDgpgBAgjA8AVKEAewIDsAmBnKuwATgJaYDmAfFALxSIBQokUAQq0iulnlJgK4BbAEYQi1Oo2bQAwjM5oMOfMID2qgDYQAhpgn0GDAPRGoqJuGiIIheDAA0bRzP0Mo7qAG0HTqDIC6XEq8noSkFI4CImKOapo6mP5uHikA-LAIMNQAPmwcrDl+8i7JKe4AXHwQAG5ixqapqZXSUABKNvwawLQExGTkULlRokSDUHFauhYs7bid3ZI2wPBh-ZFCI7Hqk3qGJlCq01ZLAEx2jqzOrinegYo8+KF9FEllHumerHfcyl7DYq83mUPgEgg8vBMEoCgUD0nA7IV2PACmM5PASjCYZVMDU6piPNjcURSmVCbVifUDkd6EsAMznXwuHokmBg36rCgktJsNm8f7E-HudIyXkqbYJLmCuGZRH5QpojGClJkvGClUCoHqhhAA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
type AA<T extends string> = T
type BB<T extends number> = T
type CC<T extends boolean> = T

// x
// Type 'A' does not satisfy the constraint 'string'.(2344)
// Type 'B' does not satisfy the constraint 'number'.(2344)
// Type 'C' does not satisfy the constraint 'boolean'.(2344)
type Test<A, B, C> = 
    [A, B, C] extends [string, number, boolean]
        ? AA<A> | BB<B> | CC<C>
        : never
// ??: type Result = string | number | boolean
type Result = Test<string, number, boolean>

// o
type Test2<A, B, C> = 
    [A] extends [string]
        ? [B] extends [number]
            ? [C] extends [boolean]
                ? AA<A> | BB<B> | CC<C>
                : never
            : never
        : never

// o
type Test3<A, B, C> = 
    A extends string
        ? B extends number
            ? C extends boolean
                ? AA<A> | BB<B> | CC<C>
                : never
            : never
        : never
```

### 🙁 Actual behavior

1. In Test1 A, B and C are incompatible with type constraints. As a comparison, Test2 is passed.
2. We still can get the `Result` type even the Test1 doesn't pass the validation by the type checker

<!-- What happened, and why it was wrong -->

### 🙂 Expected behavior

1. Don't sure about Test1 or Test2 which is valid.
2. Don't sure should we get the expected Result type when the advanced type doesn't pass the checker.

<!-- What you expected to happen instead, and why -->
Repository: PowerToys
Issue: Revisit KBM test methods: unrelated change caused failure
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Area-Tests

### Microsoft PowerToys version

0.51

### Running as admin

- [ ] Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

From https://github.com/microsoft/PowerToys/pull/14591, a change causes these to start throwing  ShortcutErrorType::ShortcutCannotHaveRepeatedModifier from BufferValidationHelpers.cpp but with the change of just going from double modifier to triple modifier.

The change should not have caused this ripple effect.

ValidateShortcutBufferElement_ShouldReturnShortcutMaxShortcutSizeOneActionKeyErrorAndNoAction_OnSettingLastDropDownToRepeatedModifierKeyOnAColumnIfThereAre3OrMoreDropDowns
ValidateShortcutBufferElement_ShouldReturnShortcutMaxShortcutSizeOneActionKeyErrorAndNoAction_OnSettingLastDropDownToNonRepeatedModifierKeyOnAColumnIfThereAre3OrMoreDropDowns




### ✔️ Expected Behavior

test should have chances are failed but not with that failure

### ❌ Actual Behavior

failed with duplicate key error

### Other Software

_No response_
Repository: material-ui
Issue: [internal] Checklist of new opportunities with React 18 release
Labels: umbrella

Tracking issue for work we should do once React 18 is released as stable

- [x] Update `peerDependencies` https://github.com/mui/material-ui/pull/32063
- [x] Update NextJs (required to use React 18 in the codebase) https://github.com/mui/material-ui/pull/33196
- [x] Update `devDependencies` (keep special cases in test for React 17 so that we can run the test suite with both versions) https://github.com/mui/material-ui/pull/33196
- [ ] Add note to docs about improved behavior of `useMediaQuery` with React 18 installed (https://github.com/mui-org/material-ui/pull/28491)
- [ ] Add note to docs about improved behavior of `useId` and therefore various `id` attributes (https://github.com/mui-org/material-ui/pull/26489, https://github.com/mui-org/material-ui/pull/29782)
- [ ] Add guide for React 18 
    Probably only streaming rendering needs attention (https://github.com/reactwg/react-18/discussions/113#discussioncomment-1672153)
Repository: yt-dlp
Issue: remove successfully downloaded items from --batch-file
Labels: enhancement

### Checklist

- [X] I'm reporting a feature request
- [X] I've verified that I'm running yt-dlp version **2021.11.10.1**. ([update instructions](https://github.com/yt-dlp/yt-dlp#update))
- [X] I've searched the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues including closed ones. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)

### Description

I append some lines for --batch-file.
Then I need option to remove lines which already downloaded. Because I don't need them anymore.
Or option to move it to other file. It creates possibility to check url before downloading if it loaded before.
Repository: yt-dlp
Issue: Option to save problematic links into file
Labels: enhancement

### Checklist

- [X] I'm reporting a feature request
- [X] I've verified that I'm running yt-dlp version **2021.11.10.1**. ([update instructions](https://github.com/yt-dlp/yt-dlp#update))
- [X] I've searched the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues including closed ones. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)

### Description

When --batch-file used there is no way to save problematic links which require attention into different file
Repository: pytorch
Issue: [DDP] Verify ignored parameter names in debug mode during init
Labels: oncall: distributed,triaged,better-engineering,module: c10d,Stale

## Feature

We saw the following issue in DDP cause a hard-to-debug hang:

1. Different set of ignored parameters across different ranks (via private ignore parameters API)
2. Rank 0 broadcasts the model to rest of the ranks, and then proceeds to next collective (barrier)
3. Some ranks have larger broadcast tensors, this causes a collective mismatch, but since 0 has finished broadcasting its tensor bytes, it can move on, the other ranks get stuck. 
4. Eventual timeout due to some ranks being stuck in broadcast().

This was eventually discovered and root caused with TORCH_DISTRIBUTED_DEBUG=DETAIL flag, but the application bug could've easily been root caused if in debug mode, we verified the set of unused parameters across ranks, so we should add this feature to the debug mode.

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang
Repository: flutter
Issue: [google_maps_flutter_web] Dispose: NoSuchMethodError: method not found: 'x=null' on null
Labels: p: maps,platform-web,package,a: production,P2,team-web,triaged-web

## Steps to Reproduce

Unsure how to reproduce, was found in Sentry several times, for various users.

[Sentry link](https://sentry.io/share/issue/9ca0b7b80a9c4bfd82ee77bdc4f392de/)

Following StackTrace is on Safari Safari 14.1.2

```
… -cache/hosted/pub.dartlang.org/google_maps_flutter_web-0.3.2/lib/src/google_maps_controller.dart in _GoogleMapState.dispose at line 417:5

/root/.pub-cache/hosted/pub.dartlang.org/google_maps_flutter-2.1.1/lib/src/controller.dart in _wrapJsFunctionForAsync at line 297:40

org-dartlang-sdk:///lib/_internal/js_runtime/lib/async_patch.dart in _wrapJsFunctionForAsync.<anonymous function> at line 317:19
org-dartlang-sdk:///lib/_internal/js_runtime/lib/async_patch.dart in _awaitOnObject.<anonymous function> at line 342:23
org-dartlang-sdk:///lib/_internal/js_runtime/lib/async_patch.dart in _rootRunUnary at line 293:19
org-dartlang-sdk:///lib/async/zone.dart in _rootRunUnary[function-entry$5] at line 1436:46
org-dartlang-sdk:///lib/async/zone.dart in _CustomZone.runUnary at line 1434:3
org-dartlang-sdk:///lib/async/zone.dart in _FutureListener.handleValue at line 1334:34
org-dartlang-sdk:///lib/async/future_impl.dart in _Future._propagateToListeners at line 124:29
org-dartlang-sdk:///lib/async/future_impl.dart in _Future._addListener.<anonymous function> at line 796:13
org-dartlang-sdk:///lib/async/future_impl.dart in _rootRun at line 466:9
org-dartlang-sdk:///lib/async/zone.dart in _rootRun[function-entry$4] at line 1428:12
org-dartlang-sdk:///lib/async/zone.dart in _CustomZone.run at line 1419:3
org-dartlang-sdk:///lib/async/zone.dart in _CustomZone.runGuarded at line 1327:34
org-dartlang-sdk:///lib/async/zone.dart in _CustomZone.bindCallbackGuarded.<anonymous function> at line 1236:7
org-dartlang-sdk:///lib/async/zone.dart in _microtaskLoop at line 1276:23
org-dartlang-sdk:///lib/async/schedule_microtask.dart in _startMicrotaskLoop at line 40:12
org-dartlang-sdk:///lib/async/schedule_microtask.dart in _AsyncRun._initializeScheduleImmediate.internalCallback at line 49:5
org-dartlang-sdk:///lib/_internal/js_runtime/lib/async_patch.dart in invokeClosure at line 49:10
org-dartlang-sdk:///lib/_internal/js_runtime/lib/js_helper.dart in convertDartClosureToJS at line 1807:14
org-dartlang-sdk:///lib/_internal/js_runtime/lib/js_helper.dart in <fn> at line 1839:1
```

```
  /// Disposes of this controller and its resources.
  ///
  /// You won't be able to call many of the methods on this controller after
  /// calling `dispose`!
  void dispose() {
    _widget = null;
    _googleMap = null;
    _circlesController = null;
    _polygonsController = null;
    _polylinesController = null;
    _markersController = null;
```
Repository: flutter
Issue: Chip delete button tap target does not meet platform recommended tap target size
Labels: framework,f: material design,a: accessibility,team-design,triaged-design

Reopening #42455 `Chip delete button tap target is too small.` 

## Steps to Reproduce

<!-- Please include full steps to reproduce so that we can reproduce the problem. -->

1. Add `androidTapTargetGuideline` test case to `packages/flutter/test/material/chip_test.dart`. See code below.
    ```dart
      testWidgets('delete button tap target complies with minimum tap target guideline', (WidgetTester tester) async {
        final SemanticsHandle handle = tester.ensureSemantics();
        final UniqueKey deleteKey = UniqueKey();
        await tester.pumpWidget(
          _wrapForChip(
            child: Column(
              children: <Widget>[
                Chip(
                  label: const Text('Label'),
                  deleteIcon: Icon(Icons.delete, key: deleteKey),
                  onDeleted: () { },
                ),
              ],
            ),
          ),
        );

        await expectLater(tester, meetsGuideline(androidTapTargetGuideline));

        handle.dispose();
      });
    ```
2.  Execute `cd packages/flutter` and `flutter test flutter/test/material/chip_test.dart` 

**Expected results:** <!-- what did you want to see? -->
- All tests pass

**Actual results:** <!-- what did you see? -->
- `delete button tap target complies with minimum tap target guideline [E]` fails with 
    ```
    Expected: Tappable objects should be at least Size(48.0, 48.0)
    Actual: <Instance of 'WidgetTester'>
    Which: SemanticsNode#5(Rect.fromLTRB(90.0, 12.0, 114.0, 36.0), actions: [tap], flags: [isButton,
  isFocusable], label: "Delete", textDirection: ltr): expected tap target size of at least Size(48.0,
  48.0), but found Size(24.0, 24.0)
            See also: https://support.google.com/accessibility/android/answer/7101858?hl=en
    ```


<details><summary>Flutter Doctor</summary>
<!-- Finally, paste the output of running `flutter doctor -v` here. -->

```
[✓] Flutter (Channel unknown, 2.6.0-12.0.pre.805, on Debian GNU/Linux rodete 5.10.46-5rodete1-amd64, locale en_US.utf8)
    • Flutter version 2.6.0-12.0.pre.805 at /usr/local/google/home/abalov/flutter
    • Upstream repository unknown
    • Framework revision aee9ade8e3 (60 minutes ago), 2021-11-23 04:03:03 -0500
    • Engine revision f4cb61cefc
    • Dart version 2.16.0 (build 2.16.0-36.0.dev)
    • DevTools version 2.8.0

```

</details>
Repository: material-ui
Issue: [Select] `native` when providing `defaultValue=""` disabled `optgroup` are included as default selected option.
Labels: bug 🐛,component: select

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

When we do not provide a default value to a select, we expect the first (enabled) option available to be selected by default. This is working well but when we provide `defaultValue=""`, for some reasons, the default selected option is different.

### without `defaultValue`
- disabled `option` are **excluded** ✔
- disabled `optgroup` are **excluded** ✔

### with `defaultValue=""`
- disabled `option` are **excluded** ✔
- disabled `optgroup` are **included** ❌

so we end up having a disabled option selected by default.
I might also misunderstand how `defaultValue` works.

### Expected behavior 🤔

I'm expecting disabled `optgroup` to always be excluded when selecting a default option to display. even with `defaultValue=""`.

### Steps to reproduce 🕹

Steps:

https://codesandbox.io/s/jolly-dawn-xjpgr?file=/src/App.js:233-245

both selects have the same content but the second one have `defaultValue=""`.
observe they don't select the same option as their default selected

### Context 🔦

_No response_

### Your environment 🌎

<details>
  <summary>`npx @mui/envinfo`</summary>  System:
      OS: Linux 5.10 Ubuntu 20.04.1 LTS (Focal Fossa)
      CPU: (12) x64 Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
      Memory: 4.97 GB / 12.43 GB
      Container: Yes
      Shell: 5.8
  Binaries:
      Node: 14.15.0
      Yarn: 1.22.5
      npm: 7.5.0
  Managers:
      Apt: 2.0.
  Utilities:
      Git: 2.25.1
  Languages:
      Bash: 5.0.17
      Perl: 5.30.0
      Python3: 3.8.10
</details>
Repository: storybook
Issue: build-storybook command not exiting if process spun up by module import side-effect
Labels: bug,cra

**Describe the bug**
When running build-storybook with the `@storybook/preset-create-react-app` addon and there is a "main" entry point to the program defined within package.json that starts an express server, the process will not exit and the build-storybook command will not exit.

We have added a simple express application to `/src/server` and defined `"main": "src/server",` within the package.json. We need a way to configure the `@storybook/preset-create-react-app` to somehow ignore these types of side effects when importing the main entry point of the program - or ignore the main entry point defined within the package.json. (Or some other recommended process...)

**To Reproduce**
https://github.com/npasqua-ebsco/repro-npasqua

1. `npm install`
2. `npm run build-storybook`
3. The output should contain a `Listening on port 9999!` message and then the build-storybook command will not exit after the `info => Output directory: /x/y/z/storybook-repro/storybook-static` message due to the express server in /src/server running.

![image](https://user-images.githubusercontent.com/48683294/143053753-27f075a4-b772-4014-ace1-0f41acb7e733.png)

**System**
Environment Info:

  System:
    OS: macOS 11.6.1
    CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
  Binaries:
    Node: 14.16.1 - ~/.nvm/versions/node/v14.16.1/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 6.14.12 - ~/.nvm/versions/node/v14.16.1/bin/npm
  Browsers:
    Chrome: 96.0.4664.45
    Firefox: 94.0.1
    Safari: 15.1
  npmPackages:
    @storybook/addon-actions: ^6.4.0-rc.5 => 6.4.0-rc.5 
    @storybook/addon-docs: ^6.4.0-rc.5 => 6.4.0-rc.5 
    @storybook/addon-essentials: ^6.4.0-rc.5 => 6.4.0-rc.5 
    @storybook/addon-links: ^6.4.0-rc.5 => 6.4.0-rc.5 
    @storybook/node-logger: ^6.4.0-rc.5 => 6.4.0-rc.5 
    @storybook/preset-create-react-app: ^3.2.0 => 3.2.0 
    @storybook/react: ^6.4.0-rc.5 => 6.4.0-rc.5

**Additional context**
n/a